My Oracle Support Banner

For Invalid Refresh Token HTTP Status Code 422 Is Received Instead of 401 (Doc ID 2918596.1)

Last updated on JANUARY 04, 2023

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
HTTP status code 422 is received when invalid refresh token is used.

EXPECTED BEHAVIOR
-----------------------
HTTP status code of 401 should be received when invalid refresh token is used.

STEPS
-----------------------
The issue can be reproduced with following steps:
1. Execute /digx-auth/v1/token API with invalid refresh_token.



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.