Error: Expected BEGIN_OBJECT but was STRING in CA Access Gateway (SPS)

Products

• SITEMINDER
• CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

 

When running CA Access Gateway (SPS), when this one receives a json token from VIP Authentication Hub, it reports error:

[04/10/2023][09:09:04][6874][140258246252288][51f288c9-08a4-4fe4-a388-5233516c9e6a_1be220dd-9a5b5594-e88c86aa-a046e9ac-f6354b4c-fe][BCOIDCTokenHandler][sendIdTokenRequest][Exception occured while sending an OIDC Token Request :  java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $]
[04/10/2023][09:09:04][6874][140258246252288][51f288c9-08a4-4fe4-a388-5233516c9e6a_1be220dd-9a5b5594-e88c86aa-a046e9ac-f6354b4c-fe][BCOIDCTokenHandler][sendIdTokenRequest][Stack Trace:  com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $

Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $

Environment

 

  CA Access Gateway (SPS) 12.8SP6 on RedHat 7;

 

Cause

 

The response message headers being received are in lowercase from

https://example.example.com/common/oauth2/v1/token

which might be causing an issue in SPS code, as per RFC, the HTTP message headers can be case-insensitive (1).

 

Resolution

 

Upgrade CA Access Gateway (SPS) to 12.8SP8 when this one will be available to benefit of fixing DE563524.

 

Additional Information

 

(1)

    4.2 Message Headers