#1012 Subsystem certificate mapping conflict
Closed: migrated 3 years ago by dmoluguw. Opened 9 years ago by edewata.

Currently the subsystem certificate may be mapped into any of these users:

  • <subsystem>-<hostname>-<port> (subsystem user)
  • pkidbuser (LDAP user)

This is because both users have a description attribute containing the same certificate ID. There is no guarantee which user the certificate will actually be mapped to.

Proposed changes: the description attribute should be removed from pkidbuser so the subsystem certificate will always be mapped to the subsystem user only. The pkidbuser is only used to access the LDAP server and the certificate mapping is done using seeAlso attribute, so this change should not affect LDAP authentication.

In the future the pkidbuser might be moved into a separate subtree (ticket #1009). This will require a manual database upgrade procedure to update existing instances.


Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1577

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata