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 #2372] [FEAT]: More user and API customization #1546

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

Originally created by @jayteaftw on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2372

What would you like to see?

I was looking into using anything-llm as it seems to have a suite of features.
However, I was curious if better User authentication could be implemented (or already exists)
The two things I am looking for are

  1. Custom external login/signup auth flow.
    When a users attempts to signin, they are sent to an external web auth (in my case I am using a CAS system) and when redirected anythingLLM would look into the JSON response which contains a JWT token that has fields that could be customized

API calls being made can have custom headers attached, Our custom LLM solution utilizes the JWT token mentioned before to see if an API call is authorized so being able to pass it through any of the API calls would be ideal instead of using an API token

Note: I am a Python user with little JS experience but would be willing to help if this is something the platform could be able to support

Originally created by @jayteaftw on GitHub (Sep 25, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2372 ### What would you like to see? I was looking into using anything-llm as it seems to have a suite of features. However, I was curious if better User authentication could be implemented (or already exists) The two things I am looking for are 1) Custom external login/signup auth flow. When a users attempts to signin, they are sent to an external web auth (in my case I am using a CAS system) and when redirected anythingLLM would look into the JSON response which contains a JWT token that has fields that could be customized 2) API calls being made can have custom headers attached, Our custom LLM solution utilizes the JWT token mentioned before to see if an API call is authorized so being able to pass it through any of the API calls would be ideal instead of using an API token Note: I am a Python user with little JS experience but would be willing to help if this is something the platform could be able to support
yindo added the enhancementfeature request labels 2026-02-22 18:25:22 -05:00
yindo closed this issue 2026-02-22 18:25:22 -05:00
yindo commented 2026-02-22 18:25:22 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 25, 2024):

We are building external auth plugins where you could assign a flow like this (probably via popup and parent.postMessage listening) which will also be how SSO #1193 will function.

Track that issue for implementation since that will be how to do this since out of the box, this specification is too niche to put in the main app. It will function a lot like agent skill plugins!

@timothycarambat commented on GitHub (Sep 25, 2024): We are building external auth plugins where you could assign a flow like this (probably via popup and parent.postMessage listening) which will also be how SSO #1193 will function. Track that issue for implementation since that will be how to do this since out of the box, this specification is too niche to put in the main app. It will function a lot like agent skill plugins!
yindo changed title from [FEAT]: More user and API customization to [GH-ISSUE #2372] [FEAT]: More user and API customization 2026-06-05 14:41:20 -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 enhancement feature request
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#1546
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?