You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @djhaskin987 , indeed that would be a nice feature!
I never implemented directly OAuth, but already did it for OpenID Connect, which is really close (OIDC just does not need a secret, only the client ID is enough for performing authentication)
What will be required for you to provide OAuth?
OAuth client ID
OAuth client secret
List of users with access to the chatbot? (so people can use generic Auth provider like GitHub or Google, and still limit the user to certain user)
List of users with admin access to the chatbot (users that can change the chatbot config and add documents)
Describe the feature
I would deploy this in a heartbeat if it had OAuth. That way I could self-host this for my company.
An idea of implementation
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: