CODEWITHSUNDEEP
banno-digital-toolkit
Steve Horn
Steve Horn

Reputation: 8959

Initial call to /oidc/me provides null address response

I am utilizing the /oidc/me endpoint to obtain address information (https://jackhenry.dev/open-api-docs/consumer-api/api-reference/v0/oauth-and-openid-connect/details/#/User%20Info). I'm observing that when calling the endpoint for a given user, the address property in the response will contain null values on the first call to the endpoint. Then, on subsequent calls the address property will be populated with correct details. I've observed that the timing between the first (failed, with missing address info) call and second (successful, with address info) calls can be less than a minute apart.

What can I do to troubleshoot this problem?

Edit to provide the sequence of API requests:

  1. /a/consumer/api/v0/oidc/auth
    &scope=openid profile email
    &claims=
{
  "userInfo": {
    "https://api.banno.com/consumer/claim/shares": null,
    "https://api.banno.com/consumer/claim/customer_identifier": null,
    "address": null
}
  1. /a/consumer/api/v0/oidc/token
  2. /a/consumer/api/v0/oidc/me

Upvotes: 0

Views: 152

Answers (1)

Jaime Lopez Jr.
Jaime Lopez Jr.

Reputation: 671

We're unable to reproduce this problem based on the above description. When we try it ourselves we get the address property as expected.

Can you provide a sequence of API requests (starting from initial authentication) that result in this behavior?

The x-request-id from the headers is also helpful (see https://jackhenry.dev/open-api-docs/consumer-api/overview/troubleshooting/).

Upvotes: 0

Related Questions