[GH-ISSUE #98] OIDC/saml #67

New issue

Closed

opened 2026-02-26 17:31:13 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 17:31:13 +03:00

Owner

Originally created by @astromandev on GitHub (May 20, 2024).
Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/98

Is there an existing feature request for this?

I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

Feature to allow users to login using a custom SAML and/or OIDC provider.

Describe the solution you'd like.

This would make it possible to use an existing central userbackend (Authentik, Active Directory, Keycloak etc.) instead of having to provision new users manually in Convoy.

Additional context to this request.

No response

Originally created by @astromandev on GitHub (May 20, 2024). Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/98 ### Is there an existing feature request for this? - [X] I have searched the existing issues before opening this feature request. ### Describe the feature you would like to see. Feature to allow users to login using a custom SAML and/or OIDC provider. ### Describe the solution you'd like. This would make it possible to use an existing central userbackend (Authentik, Active Directory, Keycloak etc.) instead of having to provision new users manually in Convoy. ### Additional context to this request. _No response_

kerem

2026-02-26 17:31:13 +03:00

closed this issue
added the
enhancement

question
labels

kerem commented

2026-02-26 17:31:14 +03:00

Author

Owner

@ericwang401 commented on GitHub (Jun 28, 2024):

Not exactly a priority at the moment, but it would be helpful if you could do a couple of things for me.

Research difference between OIDC, OAuth, and SAML.
How would user sync work? Suppose a user was deleted in your central backend. What should Convoy do with the user it created too? And how would the central user backend communicate the changes to Convoy?
Building off of above. I don't know if these providers have a name field, but suppose they do and a user changes them in the central user backend. Is there something in the standard for these providers to communicate changes?

@ericwang401 commented on GitHub (Jun 28, 2024): Not exactly a priority at the moment, but it would be helpful if you could do a couple of things for me. 1. Research difference between OIDC, OAuth, and SAML. 2. How would user sync work? Suppose a user was deleted in your central backend. What should Convoy do with the user it created too? And how would the central user backend communicate the changes to Convoy? 3. Building off of above. I don't know if these providers have a name field, but suppose they do and a user changes them in the central user backend. Is there something in the standard for these providers to communicate changes?

kerem commented

2026-02-26 17:31:14 +03:00

Author

Owner

@ericwang401 commented on GitHub (Jul 10, 2024):

Doesn't seem like those questions were ever answered. This feature won't be planned.

@ericwang401 commented on GitHub (Jul 10, 2024): Doesn't seem like those questions were ever answered. This feature won't be planned.

kerem referenced this issue

2026-02-26 17:31:30 +03:00

[PR #67] Update api-application.php #113