When no transition parameter is specified in CS.cfg tokendb.allowedTransitions, TPS UI asks for user name and password even if valid TPS admin cert is imported to the browser.
Steps to Reproduce:
1. Edit TPS CS.cfg, remove all the transitions from tokendb.allowedTransitions 2. Restart the TPS 3. Access the UI page of TPS https://<hostname>:<tps_port>/tps/ui/
Actual results:
Asks for user name password.
Expected results:
It should allow to access TPS UI.
Additional info:
It doesn't allow to access UI even if entered the username and password for admin.
Per CS/DS Meeting of 05/23/2016: 10.3.2 - (corner case) edewata will investigate
The token transitions are now validated in ticket #2334 so if the list is empty the TPS subsystem will not start and it will no longer ask for username & password.
Fixed in master:
Metadata Update from @myusuf@redhat.com: - Issue assigned to edewata - Issue set to the milestone: 10.3.2
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/2446
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.