Getting authRequestID v1 instead of authRequestId v2. Due to which createCallbackUrl API is failing.
We are encountering an issue where the authRequestID field is being returned in the v1 format (capital "ID") instead of the expected v2 format authRequestId (camelCase). This mismatch is causing the createCallbackUrl API to fail, as it appears to be strictly expecting the v2-compliant field name.
2 Replies
Hi @Nik, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. Finalize an Auth Request and get the callback URL. (1) : This shows the v2 API endpoint that expects
authRequestId as a path parameter for finalizing auth requests.
2. [Bug]: OAauth authRequestsIds from the Zitadel API are not handled anymore since they have no "oidc_" prefix (2) : This GitHub issue discusses similar problems with authRequestId format handling in the TypeScript SDK.
To learn more, see the sources I considered:
[1] Finalize an Auth Request and get the callback URL.
[2] [Bug]: OAauth authRequestsIds from the Zitadel API are not handled anymore since they have no "oidc_" prefix
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.
Got it. Tagging @Rajat for additional help.
Got it. Tagging @Rajat for additional help.
Got it. Tagging @Rajat for additional help.hey @Nik thanks a lot for your question, I will take a look at it. Can you pls share the URL returned?.