UdnPwdDirAuth authentication plugin instance is not working
Steps to Reproduce:
1. Create an authentication plugin instance UserDnEnrollment with UdnPwdDirAuth authentication plugin 2. Create a profile to use UserDnEnrollment 3. Enable the profile 4. Access the profile through the EE page
Actual results:
Sorry, your request is not submitted. The error code is "Authentication Manager UserDnEnrollment Not Found".
Expected results:
Profile using the authentication plugin should be usable or the plugin should be removed from console
Additional info:
CS.cfg has the following: auths.instance.UserDnEnrollment.dnpattern= auths.instance.UserDnEnrollment.ldap.ldapconn.host=localhost auths.instance.UserDnEnrollment.ldap.ldapconn.port=389 auths.instance.UserDnEnrollment.ldap.ldapconn.secureConn=false auths.instance.UserDnEnrollment.ldap.ldapconn.version=3 auths.instance.UserDnEnrollment.ldap.maxConns= auths.instance.UserDnEnrollment.ldap.minConns= auths.instance.UserDnEnrollment.ldapByteAttributes= auths.instance.UserDnEnrollment.ldapStringAttributes= auths.instance.UserDnEnrollment.pluginName=UdnPwdDirAuth CA debug log messages when the profile is accessed from the EE page [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet:service() uri = /ca/ee/ca/profileSelect [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet::service() param name='profileId' value='test' [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: caProfileSelect start to service. [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: ProfileSelectServlet: start serving [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: in auditSubjectID [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: auditSubjectID auditContext null [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: in auditGroupID [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: auditGroupID auditContext null [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: checkACLS(): ACLEntry expressions= user="anybody" [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: evaluating expressions: user="anybody" [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: evaluated expression: user="anybody" to be true [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: DirAclAuthz: authorization passed [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: SignedAuditEventFactory: create() message=[AuditEvent=AUTHZ_SUCCESS][SubjectID=$Unidentified$][Outcome=S uccess][aclResource=certServer.ee.profile][Op=read] authorization success [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: SignedAuditEventFactory: create() message=[AuditEvent=ROLE_ASSUME][SubjectID=$Unidentified$][Outcome=Suc cess][Role=<null>] assume privileged role [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: ProfileSelectServlet: SubId=profile [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: ProfileSelectServlet: profileId=test [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: ProfileSelectServlet: keyArchivalEnabled is true [20/Aug/2015:10:39:39][http-bio-30044-exec-9]: CMSServlet: curDate=Thu Aug 20 10:39:39 EDT 2015 id=caProfileSelect time=1
Per decision made on 08/31/2015 - 10.3.
Per Bug Triage of 05/05/2016: 10.3.2
NOTE: Jack. - try to remove this plugin so that it is no longer supported
commit b32aae9f0923e0d9fb4da12b45f478552fb53676 Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com Date: Tue Jun 7 16:39:40 2016 -0700
UdnPwdDirAuth authentication plugin instance is not working. Ticket #1579 : UdnPwdDirAuth authentication plugin instance is not working. Since this class no longer works, we felt it best to just remove it from the server. This patch removes the references and files associated with this auth method.
Closing:
Metadata Update from @rpattath: - Issue assigned to jmagne - Issue set to the milestone: 10.3.3
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/2138
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.