Many developers will need a front-end login/authentication that integrates with the back-end. One option is Amplify authentication, but the downside is it requires a Javascript front-end. To do so we could look to making a Typescript front-end folder that branches off of the mckaywrigely/chatbot-ui project.
Amplify Auth has the added benefit of allowing developers to identify which user is currently accessing the front-end allowing them to customize the chatbot with multiple features such as: allowing a user to access previous conversations in the left-hand menu and ensuring a user only has access to their own data.
Another benefit of the mckaywrigely/chatbot-ui project front-end is we can add further features later on such as allowing a user to select certain tools (similar to GPT Plugins).
Upon further consideration I think it is better to adopt Next Auth with Cognito as the provider as detailed here. This approach offers a lightweight authentication solution, eliminating the need to wrap the application in Amplify.
Many developers will need a front-end login/authentication that integrates with the back-end. One option is Amplify authentication, but the downside is it requires a Javascript front-end. To do so we could look to making a Typescript front-end folder that branches off of the mckaywrigely/chatbot-ui project.
Amplify Auth has the added benefit of allowing developers to identify which user is currently accessing the front-end allowing them to customize the chatbot with multiple features such as: allowing a user to access previous conversations in the left-hand menu and ensuring a user only has access to their own data.
Another benefit of the mckaywrigely/chatbot-ui project front-end is we can add further features later on such as allowing a user to select certain tools (similar to GPT Plugins).