References
CPS-1963 - Getting issue details... STATUS
https://ldap.com/ldap-dns-and-rdns/
Issues & Decisions
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Is FDN optional? | Is it possible to register a cmHandle without an FDN? | |
| In Hazelcast what is the key? | Is it the FDN or the cmHandleId? |
Multiple identifiers during registration
The first use case which should be handled is the storing of the new identifier ( called FDN or Fully Distinguished Name).
A fully distinguished name uniquely identifies an entry and describes its position.
To achieve this NCMP's CmHandle registration endpoint must be changed to accept a new String parameter which proposed name is fullyDistinguishedName.
Extending RestInputCmHandle object
During registration an object called RestInputCmHandle contains all the information to register new entities in the database.
The object should be extended at the top level with the new property:
RestInputCmHandle | |
|---|---|
| Field name | Type |
| cmHandle | String |
cmHandleProperties | Object |
| publicCmHandleProperties | Object |
| moduleSetTag | String |
| trustLevel | String |
| fullyDistinguishedName | String |
Save the cmHandleId and the FDN to cache
During registration the new identifier must be saved to a cache. Because it could be reused later for queries.
The new cache must implement a Map<String, String>, where the key is #TODO