Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2957] [DOCS]: Simple-SSO-Passthrough clarity #1887

New Issue
Closed
opened 2026-02-22 18:27:00 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:27:00 -05:00
Owner
Copy Link
Copy Source

Originally created by @ericthomas1 on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2957

Description

Hello,

I'm unclear on how to use the Simple SSO Passthrough (SSSOP) functionality. How does an org using EntraID (previously named Azure Active Directory) for authentication and authorization implement this?

Seems like we'd have to:

  • Create a parent app that our users visit
  • User clicks "Login to AnythingLLM"
  • SSSOP kicks off
  • User is logged into AnythingLLM

Feels like this doesn't quite solve the problems of:

  • Logging individual usage (prompts, responses, token costs, time spent, user identifier, etc.) using the LLM backend (in my case Azure OpenAI).
    • Because that connection is governed by the AOAI API key

We need a method to log individual usage of AnythingLLM for logging, auditing and usage statistics.

https://docs.anythingllm.com/configuration#simple-sso-passthrough

Originally created by @ericthomas1 on GitHub (Jan 9, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2957 ### Description Hello, I'm unclear on how to use the Simple SSO Passthrough (SSSOP) functionality. How does an org using EntraID (previously named Azure Active Directory) for authentication and authorization implement this? Seems like we'd have to: - Create a parent app that our users visit - User clicks "Login to AnythingLLM" - SSSOP kicks off - User is logged into AnythingLLM Feels like this doesn't quite solve the problems of: - Logging individual usage (prompts, responses, token costs, time spent, user identifier, etc.) using the LLM backend (in my case Azure OpenAI). - Because _that_ connection is governed by the AOAI API key We need a method to log individual usage of AnythingLLM for logging, auditing and usage statistics. https://docs.anythingllm.com/configuration#simple-sso-passthrough
yindo added the documentation label 2026-02-22 18:27:00 -05:00
yindo closed this issue 2026-02-22 18:27:00 -05:00
yindo commented 2026-02-22 18:27:00 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 9, 2025):

Feels like this doesn't quite solve the problems of:
Logging individual usage (prompts, responses, token costs, time spent, user identifier, etc.) using the LLM backend (in my case Azure OpenAI).
Because that connection is governed by the AOAI API key

Sure, but mostly because that is a different problem set then simply logging in via SSO. So with respect to the ability to login via SSO, the simple SSO provides a way to do so without a massive lift and maintenance on our side for something that is not core to the application's intention.

As for logging and usage, since every SSO login has a real user on AnythingLLM associated with it, the logging and metrics are possible to derive since we have them now as of #2825 - its a matter of making that reportable. But being able to login and then statistics from a user's usage are two different problems to solve 👍

@timothycarambat commented on GitHub (Jan 9, 2025): > Feels like this doesn't quite solve the problems of: > Logging individual usage (prompts, responses, token costs, time spent, user identifier, etc.) using the LLM backend (in my case Azure OpenAI). > Because that connection is governed by the AOAI API key Sure, but mostly because that is a different problem set then simply logging in via SSO. So with respect to the ability to login via SSO, the simple SSO provides a way to do so without a massive lift and maintenance on our side for something that is not core to the application's intention. As for logging and usage, since every SSO login has a real user on AnythingLLM associated with it, the logging and metrics are possible to derive since we have them now as of #2825 - its a matter of making that reportable. But being able to login and then statistics from a user's usage are two different problems to solve 👍
yindo changed title from [DOCS]: Simple-SSO-Passthrough clarity to [GH-ISSUE #2957] [DOCS]: Simple-SSO-Passthrough clarity 2026-06-05 14:43:16 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1887
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?