Better UI for TPS token policies #1671
Comments
|
Comment from mharmsen (@mharmsen) at 2014-08-18 21:01:01 Per CS/DS meeting of 08/18/2014, moving ticket to 10.2.2. |
|
Comment from mharmsen (@mharmsen) at 2014-09-18 05:00:06 Proposed Milestone: 10.3 (per CS Meeting of 09/17/2014) |
|
Comment from edewata (@edewata) at 2015-11-04 01:40:22 This requires:
If token policy configuration is to be stored in LDAP, it will require:
|
|
Comment from edewata (@edewata) at 2017-02-27 13:59:13 Metadata Update from @edewata:
|
|
Comment from mharmsen (@mharmsen) at 2017-03-03 19:23:02 Metadata Update from @mharmsen:
|
|
Comment from edewata (@edewata) at 2017-04-07 23:17:13 Metadata Update from @edewata:
|
|
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
This issue will be closed for inactivity. If the problem is still present reopen this or create a new issue. |
This issue was migrated from Pagure Issue #1108. Originally filed by edewata (@edewata) on 2014-08-15 19:38:01:
The token policies are stored as a single string containing name-value pairs. For example:
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:
Currently the list is fixed, but it could be made customizable in the future.
The text was updated successfully, but these errors were encountered: