lca25 Frequent Contributor.
Frequent Contributor.
1152 views

No Feedback to Helpdesk during 5015 Error

Hi
SSPR SSPR v4.3.0.4 b404 r39600 running in vSphere appliance

We've configured the Forgotten Password Profile Match - LDAP Search Filter to ensure the user's email attribute exists (mail=*)

If a user attempts to use the Forgotten Password link, they are denied if they do not have the mail attribute. So far so good.

However if the Helpdesk initiates a password change and enters a new password or selects a random password for a user without the mail attribute, there is no response.

Behind the scene in the logs indicate a 5015 error:

[INDENT]January 8, 2019, 10:07:15 AM GMT, FATAL, servlet.AbstractPwmServlet, {175,helpdeskguy} unexpected error: 5015 ERROR_UNKNOWN (unexpected error during action handler for 'password.pwm.http.servlet.helpdesk.HelpdeskServlet:setPassword', error: null) [xxx.xxx.xxx.xxx]
January 8, 2019, 10:07:15 AM GMT, ERROR, servlet.AbstractPwmServlet, {175,helpdeskguy} unexpected error during action handler for 'password.pwm.http.servlet.helpdesk.HelpdeskServlet:setPassword', error: null [xxx.xxx.xxx.xxx] (stacktrace follows)
java.lang.Throwable
at password.pwm.util.operations.PasswordUtility.helpdeskSetUserPassword(PasswordUtility.java:605)
at password.pwm.http.servlet.helpdesk.HelpdeskServlet.processSetPasswordAction(HelpdeskServlet.java:1301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at password.pwm.http.servlet.ControlledPwmServlet.dispatchMethod(ControlledPwmServlet.java:121)
at password.pwm.http.servlet.ControlledPwmServlet.processAction(ControlledPwmServlet.java:161)
at password.pwm.http.servlet.AbstractPwmServlet.handleRequest(AbstractPwmServlet.java:125)
at password.pwm.http.servlet.AbstractPwmServlet.doPost(AbstractPwmServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:661)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at password.pwm.http.filter.AbstractPwmFilter$PwmFilterChain.doFilter(AbstractPwmFilter.java:155)
at password.pwm.http.filter.AuthenticationFilter.processAuthenticatedSession(AuthenticationFilter.java:204)
at password.pwm.http.filter.AuthenticationFilter.processFilter(AuthenticationFilter.java:124)
at password.pwm.http.filter.AbstractPwmFilter.doFilter(AbstractPwmFilter.java:99)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at password.pwm.http.filter.AbstractPwmFilter$PwmFilterChain.doFilter(AbstractPwmFilter.java:155)
at password.pwm.http.filter.SessionFilter.processFilter(SessionFilter.java:113)
at password.pwm.http.filter.AbstractPwmFilter.doFilter(AbstractPwmFilter.java:99)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at password.pwm.http.filter.AbstractPwmFilter$PwmFilterChain.doFilter(AbstractPwmFilter.java:155)
at password.pwm.http.filter.ApplicationModeFilter.processFilter(ApplicationModeFilter.java:82)
at password.pwm.http.filter.AbstractPwmFilter.doFilter(AbstractPwmFilter.java:99)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at password.pwm.http.filter.AbstractPwmFilter$PwmFilterChain.doFilter(AbstractPwmFilter.java:155)
at password.pwm.http.filter.ObsoleteUrlFilter.processFilter(ObsoleteUrlFilter.java:52)
at password.pwm.http.filter.AbstractPwmFilter.doFilter(AbstractPwmFilter.java:99)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at password.pwm.http.filter.RequestInitializationFilter.initializeServletRequest(RequestInitializationFilter.java:238)
at password.pwm.http.filter.RequestInitializationFilter.doFilter(RequestInitializationFilter.java:162)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.github.ziplet.filter.compression.CompressingFilter.doFilter(CompressingFilter.java:263)
at password.pwm.http.filter.GZIPFilter.doFilter(GZIPFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:800)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)[/INDENT]

If we add a mail attribute and value to the user object, or remove the mail attribute from the Forgotten Password Profile Match - LDAP Search Filter, all works well.

It used to be in earlier versions that the 5015 Unknown Error prompt would be displayed to the Helpdesk person upon the password change attempt. Instead now they see nothing...no feedback. The password is changed for the user in any case however.

Is there a workaround for this? Are we the only ones with this issue?

Regards

Larry


Additional info: SSPR is configured to send the new passsword to the user's mail address.
0 Likes
3 Replies
AutomaticReply Absent Member.
Absent Member.

Re: No Feedback to Helpdesk during 5015 Error

lca25,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
lca25 Frequent Contributor.
Frequent Contributor.

Re: No Feedback to Helpdesk during 5015 Error

This is still an issue.

From what our web developers were able to see, the old 4.2 version of SSPR used Dojo javascript framework, which provided a popup window if a 5015 error was received during Helpdesk password change attempts if the necessary sms or mail attribute was missing.

The 4.3 version uses Angular javascript framework, and doesn't produce a 5015 popup even though via browser web developer tools the failure is evident.
0 Likes
Knowledge Partner
Knowledge Partner

Re: No Feedback to Helpdesk during 5015 Error

lca25;2494785 wrote:
This is still an issue.

From what our web developers were able to see, the old 4.2 version of SSPR used Dojo javascript framework, which provided a popup window if a 5015 error was received during Helpdesk password change attempts if the necessary sms or mail attribute was missing.

The 4.3 version uses Angular javascript framework, and doesn't produce a 5015 popup even though via browser web developer tools the failure is evident.


Hi Larry,

I'm sorry no one has responded to your post.

These forums are monitored by volunteers. We try to help on a best effort basis. If no one responded to your post, it is likely that no one has an answer for you.

If this is an urgent matter, I suggest you open a Service Request with Micro Focus Technical Support.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.