Getting Error "kodo.jdo.OptimisticVerificationException" While Updating Properties of SSO Identity Provider When Using RDBMS Security Store (Doc ID 3057916.1)

Last updated on NOVEMBER 12, 2024

Applies to:

Symptoms

Trying to utilize the RDBMS security store for security realm. When creating the configuration its working fine, encountered an issue while updating the Single Sign-On (SSO) identity provider configuration using the RDBMS security store in WebLogic server environment.

Steps followed:

1.Use WLST or console to configure RDBMS store in WLS

1.readDomain('C:\Oracle\Middleware\Oracle_Home\user_projects\domains\DomainHome') create('DomainHome','SecurityConfiguration')
cd('/SecurityConfiguration/DomainHome')
a=get('DefaultRealm')
cd('Realm/myrealm')
rdbms = create("myRDBMSSecurityStore", "RDBMSSecurityStore")
rdbms.setUsername('SA')
rdbms.setPasswordEncrypted('password')
rdbms.setConnectionURL('jdbc:sqlserver://ipadress:1433')
rdbms.setDriverName('com.microsoft.sqlserver.jdbc.SQLServerDriver') rdbms.setConnectionProperties('user=SA,databaseName=msdb')
updateDomain()
closeDomain()

2.Copy mssql-jdbc-8.4.1.jre8.jar to $WL_Home\server\lib

To avoid ClassNotFound Exceptions set CLASSPATH in $Oracle_Home\oracle_common\common\bin\commExtEnv.cmd

set WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%PROFILE_CLASSPATH%;%ANT_CONTRIB%\ant-contrib-1.0b3.jar;%MW_HOME%\wlserver\server\lib\mssql-jdbc-8.4.1.jre8.jar;%CAM_NODEMANAGER_JAR_PATH%

or

In SetDomainEnv.sh add PRE_CLASSPATH=$WL_Home/wlserver/server/lib/mssql-jdbc-8.4.1.jre8.jar

3. Create the RDBMS Tables in the Database by following "rdbms_security_store_sqlserver.sql" present at C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib

4. Start the Admin Server.

Connect to the console and navigate to the "Security Realm".Select "myrealm" and the RDBMS Security Store tab, will see all the configurations reflected.

5. Click on the "Providers" tab at the top of the page and can see that there are only two providers configured.

Create a new Provider. Click the "new" button. Name:SAML2IdentityAsserter .

6. Restart Admin Server, once the server is restarted, log onto the Admin Console again and navigate back to the Authentication Providers. Select the new Provider that created and from the resulting screen select the "Management" tab.

Click the "New" button to configure IDP Partner and select "New Web Single
Sign-On Identity Provider Partner"

NAME: WebSSO-IdP-Partner-0

PATH:C:\Users\Administrator\Downloads\Metadata_mycompany.xml (Customer provide this metadata file)

7. Click on newly created "WebSSO-IdP-Partner-0"

Update the description field or set the enable flag basically modify the settings and click "Save".

8. While "Saving the changes, getting below error if servers do not have the fix:

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.