This will be moved off on-hold when we have more working rather than unworking options. For now, LDAP is still the dominant provider even without SSO.
I want to consider using Keycloak as a replacement LDAP provider.
* https://www.keycloak.org/
* https://wiki.archlinux.org/title/Keycloak
I would want to implement OIDC, SAML/SSO, and LDAP providers at a minimum.
I could migrate users into Keycloak via https://www.open200.com/post/migrating-from-ldap-user-federation-to-keycloak-as-the-sole-identity-provider through federation & unsyncing, but it will mandate password changes. However, this could fix our MediaWiki instance for @lykos by using a more maintained extension.
## Working
* Gitea: OIDC Native https://docs.gitea.com/development/oauth2-provider
* MediaWiki: https://www.mediawiki.org/wiki/Extension:OpenID_Connect
* TT-RSS: https://github.com/tt-rss/tt-rss-plugin-auth-oidc
* SSH: https://github.com/IvanJosipovic/pam_oidc_auth/
* Graylog: https://go2docs.graylog.org/current/setting_up_graylog/oidc.html
## Nonworking
* Emby (pending): https://emby.media/community/index.php?/topic/114493-sso-openid/page/3/ -- would need LDAP interim
* Radius: would need LDAP continuance
* Filestash: OIDC is paid https://www.filestash.app/setup-oidc.html -- would need LDAP continuance
* InspIRCd/Anope: would need LDAP continuance
* HomeAssistant: https://github.com/christiaangoossens/hass-oidc-auth (pending) / https://github.com/orgs/home-assistant/discussions/48
## Criteria
This will be moved off on-hold when we have more working rather than unworking options. For now, LDAP is still the dominant provider even without SSO.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I want to consider using Keycloak as a replacement LDAP provider.
I would want to implement OIDC, SAML/SSO, and LDAP providers at a minimum.
I could migrate users into Keycloak via https://www.open200.com/post/migrating-from-ldap-user-federation-to-keycloak-as-the-sole-identity-provider through federation & unsyncing, but it will mandate password changes. However, this could fix our MediaWiki instance for @lykos by using a more maintained extension.
Working
Nonworking
Criteria
This will be moved off on-hold when we have more working rather than unworking options. For now, LDAP is still the dominant provider even without SSO.
Migrate from OpenLDAP to Keycloakto AniNIX/Password: Migrate from OpenLDAP to Keycloak