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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Thu, Mar 12
Thu, Mar 12
dereckson triaged T1772: Design LDAP schema for Nasqueron login and identity services as High priority.
One of the important thing to note is Keycloak federates user information from external storage.
Oct 28 2025
Oct 28 2025
| 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?
Sep 14 2025
Sep 14 2025
dereckson moved T1771: Evaluate Keycloak as identity and access management solution from Current focus to Backlog on the Product evaluation board.
Nov 6 2024
Nov 6 2024
dereckson assigned T1771: Evaluate Keycloak as identity and access management solution to MoustaphaAs.
Assigning per previous comment: @MoustaphaAs is currently working on this.
dereckson moved T1771: Evaluate Keycloak as identity and access management solution from Backlog to Current focus on the Product evaluation board.
Oct 30 2024
Oct 30 2024
Part of the answer :
https://pad.nasqueron.org/p/KeyCloak#L4
Feb 17 2023
Feb 17 2023
ASN.1 object identified (OID)
Feb 16 2023
Feb 16 2023
dereckson updated the task description for T1771: Evaluate Keycloak as identity and access management solution.
dereckson triaged T1771: Evaluate Keycloak as identity and access management solution as Normal priority.
Nasqueron DevCentral · If it had been much bigger the moon would have had a core of ice. · Powered by Phabricator