starred/nginx-ui

Fork 0

mirror of https://github.com/0xJacky/nginx-ui.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #279] Add additional SSO Options #5920

New issue

Open

opened 2026-03-01 17:08:04 +03:00 by kerem · 7 comments

kerem commented

2026-03-01 17:08:04 +03:00

Owner

Originally created by @DenisKevljanin on GitHub (Feb 9, 2024).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/279

Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given.
You could also think about utilizing https://next-auth.js.org.

Originally created by @DenisKevljanin on GitHub (Feb 9, 2024). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/279 Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given. You could also think about utilizing https://next-auth.js.org.

kerem added the

enhancement

label

2026-03-01 17:08:04 +03:00

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@jearton commented on GitHub (Feb 19, 2024):

or think about utilizing Keycloak

@jearton commented on GitHub (Feb 19, 2024): or think about utilizing Keycloak

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@tranthibichhlieu commented on GitHub (Oct 18, 2024):

or zitadel

@tranthibichhlieu commented on GitHub (Oct 18, 2024): or zitadel

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@nomeguy commented on GitHub (Oct 18, 2024):

Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given. You could also think about utilizing https://next-auth.js.org.

Casdoor already supports OIDC and LDAP, and more like SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA, RADIUS, etc. And it provides a better integrated solution. it's handling all the dirty work. You don't need to support native OIDC, and native LDAP. Next people will ask for native SAML, ask for CAS. Finally you found your project has become a Casdoor. So this is an endless game and why involved into this and got your hands dirty at the first time? If it's the case, maybe it's better to just create a new SSO open source project.

@nomeguy commented on GitHub (Oct 18, 2024): > Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given. You could also think about utilizing https://next-auth.js.org. Casdoor already supports OIDC and LDAP, and more like SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA, RADIUS, etc. And it provides a better integrated solution. it's handling all the dirty work. You don't need to support native OIDC, and native LDAP. Next people will ask for native SAML, ask for CAS. Finally you found your project has become a Casdoor. So this is an endless game and why involved into this and got your hands dirty at the first time? If it's the case, maybe it's better to just create a new SSO open source project.

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@Hintay commented on GitHub (Nov 5, 2024):

@Hintay commented on GitHub (Nov 5, 2024): Related issue: https://github.com/0xJacky/nginx-ui/issues/163

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@baltazartroisville commented on GitHub (Jul 22, 2025):

Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given. You could also think about utilizing https://next-auth.js.org.

Casdoor already supports OIDC and LDAP, and more like SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA, RADIUS, etc. And it provides a better integrated solution. it's handling all the dirty work. You don't need to support native OIDC, and native LDAP. Next people will ask for native SAML, ask for CAS. Finally you found your project has become a Casdoor. So this is an endless game and why involved into this and got your hands dirty at the first time? If it's the case, maybe it's better to just create a new SSO open source project.

Makes no sense to me, vendor lock-in avoidance is never a bad thing. But having only Casdoor as an option is.
SAML, LDAP, etc. are mostly used for business solutions to keep compatibility with older software, OIDC is the future.

With a native OIDC implementation we could not only add Casdoor, but Authentik, Zitadel, Keycloak, Logto, etc.
Almost all Identity Solutions support native OIDC, and if someone needs all the other standards they can just as well set it up in Authentik, Keycloak, Casdoor etc. and most importantly: they can choose freely.

@baltazartroisville commented on GitHub (Jul 22, 2025): > > Currently only Casdoor is supported. A generic OIDC or LDAP provider would be great, so some flexibility is given. You could also think about utilizing https://next-auth.js.org. > > Casdoor already supports OIDC and LDAP, and more like SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA, RADIUS, etc. And it provides a better integrated solution. it's handling all the dirty work. You don't need to support native OIDC, and native LDAP. Next people will ask for native SAML, ask for CAS. Finally you found your project has become a Casdoor. So this is an endless game and why involved into this and got your hands dirty at the first time? If it's the case, maybe it's better to just create a new SSO open source project. Makes no sense to me, vendor lock-in avoidance is never a bad thing. But having only Casdoor as an option is. SAML, LDAP, etc. are mostly used for business solutions to keep compatibility with older software, OIDC is the future. With a native OIDC implementation we could not only add Casdoor, but Authentik, Zitadel, Keycloak, Logto, etc. Almost all Identity Solutions support native OIDC, and if someone needs all the other standards they can just as well set it up in Authentik, Keycloak, Casdoor etc. and most importantly: they can choose freely.

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@Tom60chat commented on GitHub (Feb 16, 2026):

Implemented in #1488

@Tom60chat commented on GitHub (Feb 16, 2026): Implemented in #1488

kerem commented

2026-03-01 17:08:05 +03:00

Author

Owner

@Tom60chat commented on GitHub (Feb 23, 2026):

@0xJacky maybe close #279 as partially resolved?

The OIDC part of #279 is now implemented. For LDAP support, #163 already exists and covers that request in more detail.

@Tom60chat commented on GitHub (Feb 23, 2026): @0xJacky maybe close #279 as partially resolved? The OIDC part of #279 is now implemented. For LDAP support, #163 already exists and covers that request in more detail.