...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
https://ldap.com/ldap-dns-and-rdns/
Issues & Decisions
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | This is an open issue | ||
| 2 | Do we need a analysis template? | is convention for (new) developers to guide them | Luke Gleeson and Toine Siebelink agreed we do to have consistent pages | 3 | This is a very important (blocking issue) |
| 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.
...
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