CA Console: edit/view of authentication instance of portalEnrollment type does not load any value that were set during creation
Steps to Reproduce:
1. Create a CA instance 2. Go to console as an admin user 3. Create an authentication instance of PortalEnrollment type with all the required fields filled in 4. Edit/View the above created instance
Actual results:
None of the values that were filled in during creation are be loaded
Expected results:
All the values that were filled in during creation must be loaded
https://bugzilla.redhat.com/show_bug.cgi?id=1250721#c5 Investigation shows that this authentication plugin was never converted to work in the profile framework. I recommend we take out the following line from CS.cfg: auths.impl.PortalEnroll.class=com.netscape.cms.authentication.PortalEnroll
so that it cannot be instantiated from the console, nor manually in CS.cfg, unless explicitly put back in.
Once we take that out, close this ticket/bug. We can open it again if it is ever needed. Apparently it has not been needed since 2005...
commit a62ab357eb759ea59ea5204a046d0cab99126000 Author: Christina Fu cfu@redhat.com Date: Wed Aug 12 09:56:49 2015 -0700
Ticket 1543 portalEnroll authentication does not load during creation from C It appears that the PortalEnroll plugin was never converted to work in the Profile Framework. This patch takes out the following line from CS.cfg: auths.impl.PortalEnroll.class=com.netscape.cms.authentication.PortalEnroll so that it cannot be instantiated from the console, nor manually in CS.cfg, unless explicitly put back in. While in CS.cfg.in, I found the NSSAuth auths.impl line having no real implementation, so I remove that too.
Separate tickets can be filed if further actions are to be taken, such as:
or
Metadata Update from @rpattath: - Issue assigned to cfu - Issue set to the milestone: 10.2.6
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/2102
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.