Unable to update person authentication script via oxtrust

By: Lukasz Golinski Account Admin 24 Jun 2022 at 9:23 a.m. CDT

8 Responses
Lukasz Golinski gravatar
Hello, I noticed such an unusual behavior on one of our environments running gluu version 4.3.1. When I try to update person authentication scripts from the admin panel (oxtrust), it fails to do so. There is no error message present on the screen and I can confirm from the devtools network console that the request to manageAuthScript.htm?cid=1 is processed correctly with 200 http response. There is no additional information in neither oxtrust nor oxauth logs that could indicate any problem. The page is refreshed, but I do not see blue popup in the right upper corner indicating that configuration has been updated. Additionally I can mention that I am able to update for example oxAuth configuration from the admin UI. The above problem happens only when trying to update person authentication scripts. Do you have any suggestions what could be the cause of this issue?
Gluu 4.3 Docker 20.1
closed

Answers

By Aliaksandr Samuseu staff 24 Jun 2022 at 12:12 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Lukasz. >The page is refreshed, but I do not see blue popup in the right upper corner indicating that configuration has been updated. Is this the only clue that makes you think the script wasn't updated? Have you tried to add some debug line to it (one that prints some text that you can see in logs later) and see if you'll encounter this output in logs when this script is triggered? May be it's just a GUI issue that the pop up is missing, while the script is actually updated?

By Lukasz Golinski Account Admin 27 Jun 2022 at 8:02 a.m. CDT

Copy
Lukasz Golinski gravatar
Hi Aliaksandr, I can confirm that the script properties are not updated. When we hit "Update" button and the page refreshes (without any error pop-up) and we check the value of the updated property, we can see that it has the previous value - no update has happened. Regards, Lukasz Golinski

By Lukasz Golinski Account Admin 27 Jun 2022 at 9:01 a.m. CDT

Copy
Lukasz Golinski gravatar
Additionally I checked the logs of the oxauth_script.log and there are no log entries upon "UPDATE" button click.

By Lukasz Golinski Account Admin 26 Jul 2022 at 10:30 a.m. CDT

Copy
Lukasz Golinski gravatar
Hi, Performed additional tests with oxTrust with DEBUG logging level. I do know if that is relevant by I can see the following entries in the logs: ``` 2022-07-26 14:20:32,533 DEBUG [ForkJoinPool.commonPool-worker-3] [org.gluu.oxtrust.service.MetadataValidationTimer] (MetadataValidationTimer.java:114) - Starting metadata validation 2022-07-26 14:20:32,533 DEBUG [ForkJoinPool.commonPool-worker-3] [org.gluu.oxtrust.service.MetadataValidationTimer] (MetadataValidationTimer.java:117) - Metadata validation finished with result: 'false' ```

By Aliaksandr Samuseu staff 01 Aug 2022 at 4:11 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Lukasz. Sorry for not posting my findings back then. I wasn't able to reproduce your issue and thought I'll get back to it after some time for another attempt, but it slipped my mind. What happened is I encountered the very same issue in latest build myself. Here is how it looked like in my case: I used a name containing spaces for the script. Script's name you specify there also serves as OIDC acr, and it seems like oxTrust won't allow it to contain special characters - but instead of explicitly saying so, it just rejects your edits altogether (so if you change some other properties on the script's page, it will ignore them too; that could make it seem like you can't update script at all). Could you may be confirm that's the issue you also encountered? I'll create github issue for it, meanwhile, it should provide some hint about what happens ofc.

By Mohib Zico Account Admin 16 Aug 2022 at 10:38 a.m. CDT

Copy
Mohib Zico gravatar
Hi Lukasz, Just touching base to know if our last comment hit your inbox or not. :-)

By Aliaksandr Samuseu staff 24 Aug 2022 at 3:30 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Lukasz. Did you have a chance to review my post above? Could you confirm that could be the conditions under which you encountered this issue?

By Lukasz Golinski Account Admin 29 Aug 2022 at 2:32 a.m. CDT

Copy
Lukasz Golinski gravatar
Hi Aliaksandr, Thank you for your reply. After your message we managed to find the issue. The problem we encountered was the following: One of the person authentication script had a property added with a blank key. That is why oxtrust was unable to save any changes to the script. When this property was deleted the update was successful. I am closing the ticket then. Lukasz

Post an answer