Ading a new profile mapper fails does not add the param mappingResolver..class_id=filterMappingResolverImpl in CS .cfg
Steps to Reproduce:
1. Add a new enarollment profile mapper from TPS Web UI 2. Enroll a token
Actual results:
Enrollment fails
Expected results:
Enrollment should be successful
Additional info:
[02/Oct/2016:19:08:21][localhost-startStop-1]: mappingResolverManager.initMappingResolverInstance: initializing classID=filterMappingResolverImpl [02/Oct/2016:19:08:21][localhost-startStop-1]: mappingResolverManager.initMappingResolverInstance: resolver instance added: pinResetProfileMappingResolver [02/Oct/2016:19:08:21][localhost-startStop-1]: mappingResolverManager.initMappingResolverInstance: initializing classID=filterMappingResolverImpl [02/Oct/2016:19:08:21][localhost-startStop-1]: mappingResolverManager.initMappingResolverInstance: resolver instance added: keySetMappingResolver Property mappingResolver.enrollTempProfileMappingResolver.class_id missing value at com.netscape.cmscore.base.PropConfigStore.getString(PropConfigStore.java:258) at org.dogtagpki.server.tps.mapping.MappingResolverManager.initMappingR esolverInstances(MappingResolverManager.java:90) at org.dogtagpki.server.tps.TPSSubsystem.startup(TPSSubsystem.java:271) at com.netscape.cmscore.apps.CMSEngine.startupSubsystems(CMSEngine.java:1914) at com.netscape.cmscore.apps.CMSEngine.startup(CMSEngine.java:1355) at com.netscape.certsrv.apps.CMS.startup(CMS.java:200) at com.netscape.certsrv.apps.CMS.start(CMS.java:1617) at com.netscape.cms.servlet.base.CMSStartServlet.init(CMSStartServlet.java:114) at javax.servlet.GenericServlet.init(GenericServlet.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce ssorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:288) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:285) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:549) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:320) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:175) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:124) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1270) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1195) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1085) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardConte xt.java:5318) at org.apache.catalina.core.StandardContext.startInternal(StandardConte xt.java:5610) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899) at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:133) at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(Contai nerBase.java:156) at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(Contai nerBase.java:145) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:873) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:679) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConf ig.java:1966) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [02/Oct/2016:19:08:21][localhost-startStop-1]: CMSEngine.shutdown() [02/Oct/2016:19:08:21][localhost-startStop-1]: Destroying LdapBoundConnFactory(DirAclAuthz)
Per PKI Bug Council Meeting of 10/04/2016: 10.4
Metadata Update from @rpattath: - 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/2615
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)