Problem: Using webPass or standard form for Single Sign-On (SSO), it submits the credentials but because of bad/wrong credentials it gets stuck in a loop continually submitting credentials.
Cause: Single Sign-On (SSO) forms use a URL trigger to know when to submit the credentials. Some websites do not redirect the user to a failed login page after a bad attempt and simply reload the page. webNetwork will see that trigger again and try to submit again.
Solution(s): Make both the form trigger URL and startup URL unique by adding a parameter.
For example, add a ?junk=x to end of URL. Make sure to test URL with parameter in browser before applying to form object. You want to make sure it loads the page successfully. You will also want to test a failed attempt to make sure it does not keep the extra parameter. If the parameter stays after a failed attempt, we would try to submit again.
Example:
Base URL - https://customer.lenovosoftware.com/LoginPolicy.jsp
Startup URL w/ parameter - https://customer.lenovosoftware.com/LoginPolicy.jsp?junk=x
Trigger URL w/ parameter - https://customer.lenovosoftware.com/LoginPolicy.jsp\?junk=x
The characters '?' and '&' must be escaped in the Trigger URL with a '\' character.
webPass form:
- Go to webAdmin
- Expand Application Admin
- Click on desired form object
- Add the parameter to Startup URL
- Add the parameter to Login URL
- Add the parameter to Trigger URL (remember to escape '?' character)
- Click Save button
- Reload application (if applicable)
- Logout
- Login
- Test
Client form:
- Go to webAdmin
- Go to Application Admin
- Click on desired application object
- Add the parameter to Startup URL
- Click Save button
- Expand application
- Click on desired form object
- Add the parameter to Form Trigger (remember to escape '?' character)
- Reload application
- Test
keywords: sso lockout