Issue with GCLB cookie coming in as response header from API response of a webservice

Hi Everyone,

We are running on IdentityIQ 8.3P2 and trying to onboard an application using webservice connector.
We are using No/Custom Authentication and passing the username and password in JSON body to get the token and saving it in the application to be used by other operations.

The problem is, the API response send a cookie as part of response and test connection fails with the error:

{“status”:-1073741823,“error”:“java.lang.IllegalArgumentException: Cookie name [[version: 0][name: GCLB][value: CLWzQADIu–_9gEQAw][domain: ][path: /][expiry: Wed Dec 18 10:26:00 UTC 2024]] is a reserved token”,“errorDetails”:null}

When I make a call from postman, I can see a response header for GCLB cookie is being added after getting the API call response.

Another Issue we have noticed is, during aggregation, the No/Custom Authentication endpoint is being called repetitively. This is causing issues on the application side as fetching token for each aggregation call is not feasible.

Any help will be much appreciated!
Thanks!

Hi @praveen_s_03,

I never try, but you can try to manage it in the after operation rule working on rawResponseObject. You can convert in a map with:

Map response = (Map) JsonUtil.toMap(rawResponseObject);

and get the cookies. Also, you can save the token and clean the cookies and resolve the error.

It could depends if you partitioning or paging.

Hi, Thanks for the input @enistri_devo . I already tried that but was getting the same error. So had to eventually switch to Oauth2.0 client credential authentication route.

@praveen_s_03 you can use before operation rule and requestendpoint u can add the header. it will help you to resolve issue and less dependency on custom auth rule outcome.
you can call method get the cookie and add that cookie and then return so there will be no issue.