PWM 5015 ERROR_UNKNOWN

[jurb...@maine207.org]

Hello,

Thank you for making the PWM project available, it's a great service to offer our students.

I have one issue that I'm having difficulty resolving.

Any time a "continue" button is clicked a redirect to : public/command fails with error 5015
(in chrome you don't see the error, just a blank page)

This action corresponds to an error in the error log : 5015 ERROR_UNKNOWN (unknown command sent to CommandServlet: )

The service is successfully updating security questions to a remoteDB and successfully updating passwords to our AD.

Our environment is a Windows 2012 server, and I've had this issue occur in both tomcat 7 and 8.5

Any advice would be much appreciated.

[jurb...@maine207.org]

Just pinging this up to keep it alive, we're still seeing this issue. Thanks.

[Jason Rivard]

Have you set the forwardUrl or logoutUrl to something weird?

[jurb...@maine207.org]

On Sunday, September 4, 2016 at 3:32:45 PM UTC-5, Jason Rivard wrote:
> Have you set the forwardUrl or logoutUrl to something weird?
>

Thanks for the reply Jason, I do not have anything set under forwardUrl or logoutURL

[herberts...@knowledgeprice.com]

Running into the same issue here. Was working fine a while ago. The only cause I could think of is that I changed my pwm tomcat context from webapps/pwm to webapps/ROOT. The forwardUrl and logoutUrl are set to the defaults.

[jurb...@maine207.org]

That's interesting, I too changed my webapps/pwm to webapps/ROOT, however I have another instance of PWM running with a different domain and it does not encounter the issue and it too is under webapps/ROOT. I think the major difference between my two instances is the one that doesn't have the issue only connects to one DC, I don't think that really matters though.

[jurb...@maine207.org]

looking a bit more into it, it looks like whenever there is an issue the log will show :

event.AuditService, audit event:

and perpetratorID for the recently authenticated user, and the guid's don't match.

[jurb...@maine207.org]

looking further still, the trace log shows not paramaters for GET requests :

TRACE, http.PwmRequest, {10481,testuser} GET request for: /public/command (no params)

[jurb...@maine207.org]

I believe Jason's forwardurl and logouturl suggestion may have been on the right path, though I did not see any changes in those field.

After Herberts comments I decided to just reinstall and this time did not change the directory to ROOT, I left it pwm, and everything is fine now (no more 5015 error).

In my windows ROOT directory I added an index.jsp with a redirect :
response.sendRedirect("https://password.mydomain.org/pwm");

everything is working great now, for anyone else who is troubleshooting this ia appears my issue arose from renaming pwm.war to root.war, and at some point GET wasn't working and the user authentication failed, and a force logout occurred.

Good luck, thanks to all who posted.

[herberts...@knowledgeprice.com]

More of a workaround than a solution sadly. Seems a bit silly to have to include /pwm directory in your address, when you already know that you're accessing password management by using the sub-domain "password" (or "pwm" in my case).
Still looking for a solution to this issue.

[herberts...@knowledgeprice.com]

A workaround I found was to set forward Url setting to something like "mysite.com/private" instead of the default. Hopefully, this will not present other problems.

[Jason Rivard]

Is there a stacktrace in the log associated with this error?

[herberts...@knowledgeprice.com]

On Wednesday, October 26, 2016 at 2:59:24 AM UTC+3, Jason Rivard wrote:
> Is there a stacktrace in the log associated with this error?
>
> On Friday, October 21, 2016 at 6:02:46 AM UTC-4, herberts...@knowledgeprice.com wrote:A workaround I found was to set forward Url setting to something like "mysite.com/private" instead of the default. Hopefully, this will not present other problems.  

This is trace after the "cancel" button gets clicked on New User Registration, where the captcha verification takes place, the URL results to http://192.168.99.100:12980/public/command?processAction=continue leading to a blank page.

2016-10-26T06:30:56Z, TRACE, http.PwmRequest, {1} GET request for: /public/command [192.168.99.1]
processAction='continue'
2016-10-26T06:30:56Z, TRACE, servlet.CommandServlet, {1} received request for action continue [192.168.99.1]
2016-10-26T06:30:56Z, TRACE, servlet.CommandServlet, {1} redirecting user to forward url: [192.168.99.1]
2016-10-26T06:30:56Z, TRACE, state.CryptoCookieLoginImpl, {1} wrote LoginInfoBean={"a":false,"p":"*hidden*","t":"UNAUTHENTICATED","af":[],"rq":"2016-10-26T06:30:56Z","g":"iuqjkc8nk4QDYiaotj2hNOZEuak1ZvFvOyfxvPng5vD2Juh34wjo5FWKLwT6lggaMnQVouHF","c":4,"lf":[]} [192.168.99.1]
2016-10-26T06:30:56Z, TRACE, http.PwmRequest, {1} GET request for: /favicon.ico (no params) [192.168.99.1]

[jurb...@maine207.org]

That is similar to my TRACE as well

[jared...@gmail.com]

I'm seeing this on a brand new install (Ubuntu).

Are there any fixes out there?

[Robert Meany]

Just started experiencing the exact same issue on my new installation.  I was experiencing the problem with /pwm as the default directory too though.  I was using a redirect statement in my tomcat server to send folks from the root path to /pwm/ ...  I'll probably use the forward url workaround for now.