TPS UI: Authorization should fail when trying to login as a user not associated with any TPS role
Steps to Reproduce:
Enroll for a user cert through the EE page of the root CA instance. Approve the cert request and Import the cert to the browser. Add a TPS user with parameter userId=notAnAgent1,firstname=test,lastname=notagent1,No Role selected. Add the cert to the user Login to system as non-root user. Open the browser and enter the TPS Subsystem URL. Ex: https://test.redhat.com:<secure-port/tps Provide notAnAgent1 Certificate
Actual results:
[AuditEvent=AUTH_SUCCESS][SubjectID=tpsNonAgent][Outcome=Success][AuthMgr=certU serDBAuthMgr] authentication success [AuditEvent=AUTHZ_SUCCESS][SubjectID=tpsNonAgent][Outcome=Success][aclResource= certServer.tps.account][Op=login][Info=AccountResource.login] authorization success
Expected results:
Authorization should fail
Per CS/DS meeting of 07/13/2015: 10.3
The UI should display an authorization failure.
This case is an corner case. Generally the TPS admin needs to make sure the users always have a TPS role.
Metadata Update from @rpattath: - 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)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - 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/2038
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.