#1108 Better UI for TPS token policies
Closed: migrated by dmoluguw. Opened by edewata.

The token policies are stored as a single string containing name-value pairs. For example:

RE_ENROLL=YES&RENEW=YES

Currently user has to enter policies in this format. It would be nice for the UI to provide a more user-friendly interface to configure the policies for individual tokens. Valid policy settings for individual tokens are: YES, NO, and unset, so the UI can provide radio buttons to select these values.

There should be another interface to configure the default token policies. The valid values will be: YES and NO. If a policy is unset in the individual token, it will use the default policy.

Here is the list of token policies:

  • RE_ENROLL
  • RENEW
  • FORCE_FORMAT
  • PIN_RESET
  • RESET_PIN_RESET_TO_NO

Currently the list is fixed, but it could be made customizable in the future.


Per CS/DS meeting of 08/18/2014, moving ticket to 10.2.2.

Proposed Milestone: 10.3 (per CS Meeting of 09/17/2014)

This requires:

  • adding new UI to display/manage token policies
  • adding new UI to customize token policies

If token policy configuration is to be stored in LDAP, it will require:

  • creating the LDAP schema
  • modifying the installer to create the LDAP entries
  • modifying the server to load the LDAP entries
  • writing database upgrade script

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

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

Metadata Update from @edewata:
- Issue set to the milestone: FUTURE (was: 10.4)

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

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)

Metadata