Password Reset Page Results in Error

By: Ni Rpg user 31 Jan 2020 at 1:11 a.m. CST

10 Responses
Ni Rpg gravatar
When a user goes the "Forgot Your Password?" function, they receive an email to a valid page that allows them to input a new password. Our Gluu installation links them to a page that results in an error 404 page with no visible or obvious logs to be found that could explain the resulting error. ``` HTTP ERROR 404 Problem accessing /identity/resetPassword/pt0p5s284j77b3jf. Reason: Not Found Powered by Jetty:// 9.4.12.v20180830 ```
Gluu Other Ubuntu 18.04
closed

Answers

By Mohit Mali staff 31 Jan 2020 at 2:15 a.m. CST

Copy
Mohit Mali gravatar
Hi, Thanks for reaching out gluu support, i will assist you on this ticket. can you post all the step you are following so i can recreate this issue. thanks and regards mohit mali

By Ni Rpg user 31 Jan 2020 at 11:03 p.m. CST

Copy
Ni Rpg gravatar
I uploaded screenshots to the attached link. We are working on tracking down any logs that seem relevant. We can also try to produce configuration files that may be relevant, but you may need to give specific guidance on what would be helpful.
Video or screenshot link

By Ha Ro user 01 Feb 2020 at 2:18 a.m. CST

Copy
Ha Ro gravatar
Turned up logs to DEBUG. /opt/gluu/jetty/identity/logs/oxtrust.log when click the link in the email for the password reset and hit the page: https://login.thefantasy.network/identity/resetPassword/wxvz!fhqzy0215tg Browser shows: HTTP ERROR 404 Problem accessing /identity/resetPassword/wxvz!fhqzy0215tg. Reason: Not Found Powered by Jetty:// 9.4.12.v20180830 oxtrust.log shows this: "2020-02-01 08:14:51,604 INFO [qtp99747242-18] [org.gluu.oxtrust.service.filter.AuthorizationProcessingFilter] (AuthorizationProcessingFilter.java:78) - Path is protected, proceeding with authorization processing... 2020-02-01 08:14:51,667 DEBUG [qtp99747242-18] [org.gluu.oxtrust.service.uma.UmaPermissionService] (UmaPermissionService.java:189) - Construct response: HTTP 401 (Unauthorized), ticket: 'ad5ee1f8-24ca-438b-93f9-b7926098e7eb' " Anything helpful there?

By Mohit Mali staff 03 Feb 2020 at 2:02 a.m. CST

Copy
Mohit Mali gravatar
Hi , Please upgrade to 4.0 or stick with 3.1.6. Thanks and Regards Mohit Mali

By Ha Ro user 04 Feb 2020 at 1:02 a.m. CST

Copy
Ha Ro gravatar
Are you saying that 3.1.7 is an unsupported release? Would really love to have seen something to that effect. Is there a page somewhere that states which versions are actually supported vs. not actually?

By Mohib Zico Account Admin 06 Feb 2020 at 11:56 a.m. CST

Copy
Mohib Zico gravatar
3.1.7 is supported but that fix is reflected in 4.x version. We are trying to figure out if we should release a patch for 3.1.7 or not.

By Michael Schwartz Account Admin 06 Feb 2020 at 7:57 p.m. CST

Copy
Michael Schwartz gravatar
Yes, we should patch it in the next release for 3.1.x

By Ha Ro user 06 Feb 2020 at 11:25 p.m. CST

Copy
Ha Ro gravatar
We wiped out 3.1.7 (after first making a backup) fully deep uninstalling. Setup fresh 3.1.6. That fixed the issues with the password reset, but alas now we have to set everything else back up fresh, new API keys with third parties, etc. Would definitely have preferred to be able to patch 3.1.7. Do you have an ETA on the next 3.1.x branch update? I looked at 4.x and it seemed like it was still too unstable for production use. Is that an accurate assessment, or am I mistaken? I'm considering 4.x for another location, but don't want to go through the whole setup process if it is going to need another year or so to mature before ready for prime time. Thanks for your help, very much appreciate the guidance!

By Michael Schwartz Account Admin 06 Feb 2020 at 11:31 p.m. CST

Copy
Michael Schwartz gravatar
4.1 will be out shortly.

By Mohib Zico Account Admin 07 Feb 2020 at 1:47 a.m. CST

Copy
Mohib Zico gravatar
>> Is that an accurate assessment, or am I mistaken? Mistaken, our customers went live with 4.0 already and they said it's stable. But wait for 4.1 as it's very near and we have 'upgrade' scripts available which you can use without doing reinstallation everything. >> Yes, we should patch it in the next release for 3.1.x Thanks! Talking to oxTrust dev team then.

Post an answer