Token Generation Fails with Error "java.lang.NullPointerException" During AISP Consent Creation Approval
(Doc ID 2918595.1)
Last updated on JUNE 04, 2024
Applies to:
Oracle Banking APIs - Version 21.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to approve Account Information Services Provider (AISP) consent created, following error occurs.
ERROR
-----------------------
On screen:
Error 500 - Internal sever error
In logs:
java.lang.NullPointerException
at com.ofss.digx.oauth2.utils.TokenGenerator.persistAccessToken(TokenGenerator.java:164)
at com.ofss.digx.openid.service.authcode.AuthCodeOIDC.generateCode(AuthCodeOIDC.java:239)
at com.ofss.digx.oauth2.rest.oauthpolicyadmin.AuthCode.generateCode(AuthCode.java:176)
at com.ofss.digx.oauth2.AuthCodeServlet.doPost(AuthCodeServlet.java:418)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
STEPS
-----------------------
The issue can be reproduced with following steps:
1. Third Party Providers (TPP) has 3 rows response types in DIGX_AU_RESPONSE_TYPES table
a. code
b. code id_token
c. code id_token token
2. Create Client Credential Access token /digx-auth/v1/token
3. Create consent request./v3.1/aisp/account-access-consents
4. TPP response_type with 'code id_token token'
5. Login via URL > Select account > Confirm .
6. Notice the error on screen.
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 |