-
Notifications
You must be signed in to change notification settings - Fork 150
Diagnostic with one click fix
In oxauth we can get different problems. Many of them goes as support tickets which consumes time from all - customers, support engineers, software engineers etc.
Lets consider following example:
Customer reports that authentication does not work. It opens support ticket with log where we can see:
2020-03-11 11:12:53,880 ERROR [qtp392292416-15] [gluu.oxauth.authorize.ws.rs.AuthorizeAction] (AuthorizeAction.java:251) - Failed to get CustomScriptConfiguration. auth_step: 1, acr_values: urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
Which in English means that script can't be loaded. Is it corrupted? Is it enabled? Is it valid script by design?
We can semi-automate process of resolving such issues. At the time of failure oxauth can post error with code
and parameters
to persistence (not only log it). oxtrust can show it and depending on problem propose fix.
oxauth posts :
{"error":"invalid_script", "acr":"urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport"}
oxtrust shows:
"Unable to load script urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
. It's disabled. Fix it? (Enable script)"
Or if it's corrupted:
oxtrust shows:
"Unable to load script urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
. Python script is not valid. Open script for correction?"
In this way we can guide customer and provide solution for most cases.
We should show events with proposed fix in console similar as Intelij IDEA makes it. Links are clickable and performs actions for given event.