Redirect uri in Azure B2C with query string. Error detail: URL may not contain a query string

%3CLINGO-SUB%20id%3D%22lingo-sub-2145419%22%20slang%3D%22en-US%22%3ERedirect%20uri%20in%20Azure%20B2C%20with%20query%20string.%20Error%20detail%3A%20URL%20may%20not%20contain%20a%20query%20string%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2145419%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20use%20Azure%20B2C%20OAuth%20for%20Alexa%20account%20linking%20with%20implicit%20flow.Below%20is%20the%20redirect%20url%20from%20Alexa%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Falexa.amazon.co.jp%2Fspa%2Fskill%2Faccount-linking-status.html%3FvendorId%3DXXXXXXXXXX%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Falexa.amazon.co.jp%2Fspa%2Fskill%2Faccount-linking-status.html%3FvendorId%3DXXXXXXXXXX%3C%2FA%3E%3C%2FP%3E%3CP%3EBut%20adding%20this%20gives%20below%20error%20in%20Azure%20B2C%20app.%3C%2FP%3E%3CP%3EFailed%20to%20update%20xxx-xxxxxxapp%20application.%20Error%20detail%3A%20URL%20may%20not%20contain%20a%20query%20string%3C%2FP%3E%3CP%3EI%20tried%20below%20link%20for%20solving%20this%20but%20its%20not%20working%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.aaddevsup.xyz%2F2018%2F04%2Fquery-string-is-not-allowed-in-redirect_uri-for-azure-ad%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.aaddevsup.xyz%2F2018%2F04%2Fquery-string-is-not-allowed-in-redirect_uri-for-azure-ad%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20also%20tried%20auth%20code%20grant%20flow%20with%20SPA%20in%20B2C.%20That%20is%20also%20not%20working%20with%20Alexa%20as%20it%20has%20PKCE%20-%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F64073%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F64073%3C%2FA%3E.%20I%20have%20to%20use%20Azure%20AD%20B2C.%20Any%20idea%20how%20to%20set%20up%20PKCE%20in%20Alexa%20account%20linking%3C%2FP%3E%3CP%3EAnyone%20succeeded%20in%20creating%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2145419%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%20Services%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2179288%22%20slang%3D%22en-US%22%3ERe%3A%20Redirect%20uri%20in%20Azure%20B2C%20with%20query%20string.%20Error%20detail%3A%20URL%20may%20not%20contain%20a%20query%20string%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2179288%22%20slang%3D%22en-US%22%3EJust%20adding%20my%20comment%20here%20because%20the%20post%20was%20too%20lonely.%3C%2FLINGO-BODY%3E
Occasional Visitor

I'm trying to use Azure B2C OAuth for Alexa account linking with implicit flow.Below is the redirect url from Alexa

https://alexa.amazon.co.jp/spa/skill/account-linking-status.html?vendorId=XXXXXXXXXX

But adding this gives below error in Azure B2C app.

Failed to update xxx-xxxxxxapp application. Error detail: URL may not contain a query string

I tried below link for solving this but its not working https://blogs.aaddevsup.xyz/2018/04/query-string-is-not-allowed-in-redirect_uri-for-azure-ad/

I also tried auth code grant flow with SPA in B2C. That is also not working with Alexa as it has PKCE - https://github.com/MicrosoftDocs/azure-docs/issues/64073. I have to use Azure AD B2C. Any idea how to set up PKCE in Alexa account linking

Anyone succeeded in creating this?

3 Replies
Just adding my comment here because the post was too lonely.

@arunkrishna2992 

 

We have run into the exact issue. Trying to setup azure b2c in SAP Gigya as an IDP and it does not like the callback/redirect URL because of the ? at the end. 

https://socialize.us1.gigya.com/socialize.finalizeOidcLogin?

 

Trying to work with Microsoft to see if they could allow it. It is a security risk to pass values in query string. however, we are not passing anything. just the ? which is required by SAP...

 

So far no luck, but i will reply here if we find a resolution.