#963 Outdated TPS group names
Closed: Fixed Opened by edewata.

Currently the default TPS group names are:

  • TUS Agents
  • TUS Officers
  • TUS Administrators
  • TUS Operators

The term "TUS" might be confusing to new TPS users so they should be removed. The group names will simply become Agents, Officers, Administrators, and Operators.

If backward compatibility is not a concern (ticket #957), this change can be done immediately by doing a search and replace.

If backward compatibility is a concern, an upgrade script is needed to rename the group names in the existing database (ticket #710).


Per discussion with cfu, the "TUS" most likely needs to be removed, but the new group names should be consistent with the other subsystems.

CA groups:

  • Certificate Manager Agents
  • Registration Manager Agents
  • Subsystem Group
  • Trusted Managers
  • Administrators
  • Auditors
  • ClonedSubsystems
  • Security Domain Administrators
  • Enterprise CA Administrators
  • Enterprise KRA Administrators
  • Enterprise OCSP Administrators
  • Enterprise TKS Administrators
  • Enterprise RA Administrators
  • Enterprise TPS Administrators

KRA groups:

  • Data Recovery Manager Agents
  • Subsystem Group
  • Trusted Managers
  • Administrators
  • Auditors
  • ClonedSubsystems
  • Security Domain Administrators
  • Enterprise KRA Administrators

OCSP groups:

  • Online Certificate Status Manager Agents
  • Subsystem Group
  • Trusted Managers
  • Administrators
  • Auditors
  • ClonedSubsystems
  • Security Domain Administrators
  • Enterprise OCSP Administrators

TKS groups:

  • Token Key Service Manager Agents
  • Subsystem Group
  • Trusted Managers
  • Administrators
  • Auditors
  • ClonedSubsystems

Per discussions, targeted 10.2 - 05/14 (May)

Per discussion with cfu, the groups will be renamed to:

  • TPS Agents
  • TPS Officers
  • Administrators
  • TPS Operators

master:

  • e1dc7757f9dedf41e712408196cc91902b3c5b89

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/1529

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