Default page_token for list identities yields 400 (go at least)

[vincegio]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe the bug

Suddenly got 400 issues from ListIdentities in our production service.
Boiled it down to

sdk/clients/client/go/api_identity.go

Line 2251 in 591d959

var defaultValue string = "1"

Reproducible by setting page_token=1 in a request outside of the SDK.

Reproducing the bug

1. GET /admin/identities
2. Test with the defaults from the previously linked code (page_token=1)
3. It will fail

Relevant log output

"error": {
    "code": 400,
    "status": "Bad Request",
    "request": "f643e501-9e67-99b5-9989-f02ae0b499b5",
    "reason": "The page token is invalid, do not craft your own page tokens",
    "message": "The request was malformed or contained invalid parameters"
  }
}

Relevant configuration

Version

Network

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

No response

[abdullah599]

I am facing the same issue. Hopefully, it will be resolved soon.

[abdullah599]

Worth noting that it's not limited to ListIdentities, the same invalid default page_token = "1" exists in these Execute functions as well:

• ListIdentitySchemasExecute
• ListIdentitySessionsExecute
• ListOAuth2ConsentSessionsExecute
• ListMySessionsExecute

Workaround: Explicitly pass an empty PageToken("") on every request. This sets r.pageToken to a non-nil pointer, which skips the buggy else branch that injects "1":

Example:

// Before (broken):
apiClient.IdentityAPI.ListIdentities(ctx).CredentialsIdentifier(username).Execute()

// After (works):
apiClient.IdentityAPI.ListIdentities(ctx).CredentialsIdentifier(username).PageToken("").Execute()

[francesconi]

We're running into the same issue and would be grateful for any updates regarding a resolution.

[davidspiess]

Hi @zepatrik, are you aware of this issue?

[Teilkasko]

Hi @DavudSafarli, you have marked this issue as completed, but I was not able to find a PR or a commit yet which actually removes or replaces the faulty default value "1". For our systems the described bug still persists.

Could you please give us a hint what has changed since this problem was brought up?

[DavudSafarli]

Hi! Issue got closed by some automation, which was not intended. Sorry about that.

We are aware of the issue and it'll be fixed in the upcoming release(in few days)