Yep, but it only supports GitHub OAuth. i.e. Content is either saved under no user (anonymous) or the authenticated GitHub User.

Thanks. Looks like this is purely to gatekeep internal access, but isn't ready for any oidc, or with a db backed session store.

All the best for the project, will check in later on these..

	▲	hobofan an hour ago \| parent [-]
		If you are looking for a open source Chat WebUI with support for OIDC, maybe you are interested in the one we are building?[0] We are leveraging oauth2-proxy for the login here, so it should support all OIDC-compliant IDPs, and there are some guides by oauth2-proxy on how to configure for all the bigger providers. We do have customers using it with e.g. Azure, Keycloak, Google Directory. [0]: https://erato.chat