This project handles the aspects of login and identity services for Nasqueron, including user login, credentials management, SSO, linking applications to that SSO.
For the Auth Grove software, see Auth Grove.
This project handles the aspects of login and identity services for Nasqueron, including user login, credentials management, SSO, linking applications to that SSO.
For the Auth Grove software, see Auth Grove.
It has been asserted a LDAP is the easiest deployment road for Keycloak operation, supported out of the box, without any custom development needed. If we store users in a MariaDB or PostgreSQL database, we need custom development to explain to Keycloak how to use it.
One of the important thing to note is Keycloak federates user information from external storage.
| Org | Comments |
|---|---|
| Oracle / Sun | A mess, no hierarchy description |
| Samba | .4 (but .1 for attributes, .2 for classes) + .777 for internal use |
| Wolfplex | .1 |
| Yubico | Two different top-level classes: 10 for classes, 11 for attributes |
1.3.6.1.4.1.60024.100.
Why exactly .100 and not .1 for LDAP extensions?
Assigning per previous comment: @MoustaphaAs is currently working on this.
Part of the answer :
https://pad.nasqueron.org/p/KeyCloak#L4
ASN.1 object identified (OID)