WebCenter Forms Recognition Is Not Accepting SSO Credentials
(Doc ID 2455556.1)
Last updated on NOVEMBER 29, 2023
Applies to:
Oracle WebCenter Forms Recognition - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Goal
WebVerifier has been enhanced to support Single Sign-On (SSO) user authentication. The SSO implementation will intercept the user’s login request and either gather the user credentials and authenticate the user, or accept the user as already authenticated. The SSO functionality is implemented as a generic solution to work with any SSO implementation and configuration that provides the user credential information via an HTTP header.
There are two different sessions to consider when SSO is used; the SSO session and the WebVerifier Client (WVC) session.
- The SSO session generally has longer life as it might be used for other applications and not only for WVC.
- The WVC and SSO sessions are both renewed with every server request. For example, field validation or opening the next batch. These are not renewed with client-side actions such as zooming in on the image or typing a value into form field without validating it.
When SSO authentication mode is used, the WVC session timeout must be set to a smaller value than the SSO session timeout. Otherwise, if the SSO session times out while the WVC session is still active, the user will be re-directed to the SSO login page, and any changes made in Web Verifier will be lost. To achieve this, the following parameter must be set appropriately:
<sessionState timeout="20"/>
Refer to the product documentation of your SSO provider for details how to configure the SSO session duration.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |