https://bugzilla.redhat.com/show_bug.cgi?id=154176
Description of problem: Log in to console as admin or directory manager and bring up DS console, then "Log in as New User" and auth as a regular user. On most panels the normal user can't do anything, but on the Tasks tap, the stop/start/restart buttons works. Even changing cert db passwd works too. He/she can also get to the admin console and change admin user id/passwd, and admin port, etc. Note that if a normal user run startconsole and authenticate in that way, he/she won't be able to bring up DS console at all. Only limited access to Users and Groups panel in the admin console. This is most likely not a regression, and may not be common use case anyway. The only risk is an admin user switch or give control of the consoles to a regular user this way and assumes the regular user can't do anything. How reproducible: Consistently.
batch move to milestone future
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @nkinder: - Issue set to the milestone: 389-admin,console FUTURE
Admin server/Console is deprecated, closing ticket...
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/233
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. We apologize for all inconvenience.
Login to comment on this ticket.