My Oracle Support Banner

"java.sql.SQLIntegrityConstraintViolationException" Error Observed for Refresh Token During Create Consent (Doc ID 2917546.1)

Last updated on DECEMBER 26, 2022

Applies to:

Oracle Banking APIs - Version 21.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

While creating consent for refresh token, following error occurs.

ERROR
-----------------------
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (<schema_name>.DIGX_AU_REFRESHTOKEN_CLAIMSET_PK) violated
Error Code: 1
Call: INSERT INTO DIGX_AU_REFRESHTOKEN_CLAIMSET (REFRESH_TOKEN, CLAIM_ID, VALUE) VALUES (?, ?, ?)

STEPS
-----------------------
1. Create an access token.

2. Create a Consent.

3. Create request using two claimsets.

Example: claims: { 'userinfo': { 'openbanking_intent_id': {'value': '<value>', 'essential': bool(True)} }, 'id_token':{'openbanking_intent_id': {'value': '<value>', 'essential': bool(True)}, 'acr': {'essential': bool(True), 'values': ['urn:openbanking:psd2:sca']}} }
Here userinfo and id_token are 2 claims

4. Use the authentication url and login via user.

5. After login, select the account and provide confirm and get the code.

6. Get the code from step 5 and send the code in the create token API(i.e. /digx-auth/v1/token).

7. Check the Create token API response and error in the logs.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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