cfu wrote in ticket #890:
not sure if there is a better ticket for this note, but I just found out the TPS user on KRA is in the "Data Recovery Managers" group instead of the "Trusted Managers" group. In order for TPS to talk to DRM (KRA) properly via the connector, it needs to be put in the "Trusted Managers" group, like where the CA user is. Logically, it really should be this way anyway, since the "Data Recovery Managers" group is for the actual KRA agent users. This should be fixed in the TPS installation wizard.
Proposed milestone: 10.2 May
Per CS/DS meeting of 5/5/2014, moving to milestone 10.2 (May).
Planned changes: http://pki.fedoraproject.org/wiki/Subystem_Certificates#Required_Changes
503-1-Replaced-group-for-RegisterUser.patch pki-edewata-0503-1-Replaced-group-for-RegisterUser.patch
After some testings with cfu, it's concluded that in order for the connectors to work properly the user needs to remain in the original groups.
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2 - 05/14 (May)
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/1556
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.