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
Background: Using Simple SSO - for example with external authentication service like Azure AAD - requires to link a anythingllm user with an user "owned" by the authentication service.
In most cases it is not possible to store the anythingllm's user id in that directory.
Proposed change:
Add "GET /v1/admin/usersByName/{username}" to Create or Update the user identified by that username.
Add "PATCH /v1/admin/usersByName/{username}" to Create or Update the user identified by that username.
PS: Alternatively, as the DB apparently is already ensuring uniqueness of username (as it should), refactor existing API to use the user-defined username for all API flavours.
The text was updated successfully, but these errors were encountered:
brainboutique
changed the title
[FEAT]: Support "remote identifier" for user management
[FEAT]: API - Support "remote identifier" for user management
Feb 20, 2025
brainboutique
changed the title
[FEAT]: API - Support "remote identifier" for user management
[FEAT]: API - Ease "username" for user management via API
Feb 20, 2025
What would you like to see?
Background: Using Simple SSO - for example with external authentication service like Azure AAD - requires to link a anythingllm user with an user "owned" by the authentication service.
In most cases it is not possible to store the anythingllm's user id in that directory.
Proposed change:
PS: Alternatively, as the DB apparently is already ensuring uniqueness of username (as it should), refactor existing API to use the user-defined username for all API flavours.
The text was updated successfully, but these errors were encountered: