Replies: 1 comment
-
|
@j-koehler Thank you a lot for the feedback here. We acknowledge that the auth config settings for self-hosted users have grown organically over time and may lead to confusing behaviours when used together. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature or potential improvement
User management currently feels a bit off to me. What I would dream of:
In the current implementation there is no real way to do this.
AUTH_DISABLE_SIGNUPis very strict, by even locking out any new user (e.g. new users through SSO). Leaving it untouched (-> false) colides withAUTH_DOMAINS_WITH_SSO_ENFORCEMENT, which is a blacklist of domains, so any other domain can still manually signup+login (permissions depending on the configured default org/project/role, which is was mainly configured for users through SSO to reduce manual assignments/permission checks).Disabling username+password altogether through
AUTH_DISABLE_USERNAME_PASSWORDis causing issues when using "meta accounts" (e.g. created throughLANGFUSE_INIT_USER_*), since they can't be used any longer. (But it's a workaround to enable this setting after initial setup and granting broader permissions to "real users".)So right now there is no "feels good" way to solve my initial plan. Maybe there is an easy way to solve this, maybe it's intentional as it is.
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions