Hi @ibuchanan, kinda good news, using the URL hack you suggested I get one step further
-
The authorisation page loads correctly with the correct scopes selected (see attached).
-
I click accept and get redirected to:
https://logic-apis-westus.consent.azure-apim.net/redirect?code=#############&state=%24{hKFo2SBmQnNiNHc3RG10Sk9URU5EYzZlMklmeGN2WXZ6Zlo4d6Fup2NvbnNlbnSjdGlk2SB1ZzFxRnlDdUdCWUE2UnUwdGQ4NGtRMklET2NnQ1RDY6NjaWTZIDZ6T1I5cTdtSzl5SFpMU3M2VDJPaHJRbWdjWVo2TzR5}
I’ve hashed the code just in case
I confirmed the code is valid by using it in a call to the endpoint ‘https://auth.atlassian.com/oauth/token’ with my credentials - which did return a valid access token.
Unfortunately the redirected page is blank except for the message:
{“Message”:“The request is invalid.”,“ModelState”:{“consentInfo”:[“No consent server information was associated with this request.”]}}
Any thoughts on a hack to get the redirect url working correctly?
Thanks
