IdM - Self password reset u2013 Internal Server Error

Question

Hello
We are trying to set the self password reset on IdM 7.1 SP4.
The User Interface and the Identity Center are installed on two different Was JAVA servers. When we try the reset password, it goes along well (authentication) but in the end, when we click on the u201CEndu201D button we get the following message :
500 Internal Server Error
Failed to process request. Please contact your system administrator
And the detailed error information :
java.lang.NullPointerException
        at com.sap.idm.wd.wf.task.PwdRecoverComp.SaveData(PwdRecoverComp.java:255)
        at com.sap.idm.wd.wf.task.PwdRecoverComp.MoveNext(PwdRecoverComp.java:293)
        at com.sap.idm.wd.wf.task.wdp.InternalPwdRecoverComp.MoveNext(InternalPwdRecoverComp.java:192)
        at com.sap.idm.wd.wf.task.PwdRecoverCompView.onActionNext(PwdRecoverCompView.java:165)
        at com.sap.idm.wd.wf.task.wdp.InternalPwdRecoverCompView.wdInvokeEventHandler(InternalPwdRecoverCompView.java:193)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
        at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
        at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
We thought that maybe it was because of the two different servers installation since it used to work when everything was on the same server. Did anyone ever tried the self reset password with the same configuration as we have? Or do anyone know if it is necessary for the task to work to have IdM and the portal on the same server?
Or maybe its a deploying IDMu2019s package problem?
Regards,
Clotilde

Answer 1

Hello
@Scott
Make sure you have the correct sca file deployed on the portal from your service pack and make sure that the keys.ini file is correctly set up on the portal.
About the sca, we deployed the IDMIC04_0-10007482.SCA (SP4) do we also need to deploy the IDMIC00_0.sca? (we didn't)
About the keys.ini, we deployed the same file in each server.
@Roy
Have the user prepared the Authq attributes in the identity store, and you are using the correct answers?
Yes, we only use the MX_AUTHQ_001 that we fill with the user's MX_PRIMARY_MAIL when we create it. The encryption is ok and we use the correct answer.
What are your settings on the password reset settings in the Admin MMC?
The settings are :
Identification attribute  MSKEYVALUE
No of question to show 1
No of answers required 1
Max no of attempts 3
Password creation method Automatically generate
Save the password to UME no
Which version of the NW are you running?
7.1 SP4
Did you deploy the correct version of the webui?
package SP4
Could you try to change the loglevel of the defaulttrace on tcidmjmx-app to debug, and add the section of the log
where it throws an error.
I tried to do it but I didn't find where I'm supposed to configure that. Could you please help me on that or send me a link to a documentation that would explain it?
Thanks a lot,
Clotilde