Power Platform Community Forum Thread Details

My custom connector keeps failing so I did a few tests and found out that it's the power automate settings thats mangling my url.

I generated the authentication url just like it says in the twitter docs. When i tried to input the same fields in the power automate generic oauth 2 config my url is mangled. I can make the request in python no problem. Also if i generate the url in python an paste it into the browser, also no problem.

https://twitter.com/i/oauth2/authorize?client_id=[xxx]&response_type=code&redirect_uri=https%3a%2f%2fglobal.consent.azure-apim.net%2fredirect&scope=tweet.read+tweet.write+users.read&state=e3761477-6c20-4133-9160-a961156e74e0_unitedstates-002_azure-apim.net

https://twitter.com/i/oauth2/authorize?response_type=code&client_id=[xxx]&redirect_uri=https://global.consent.azure-apim.net/redirect&scope=tweet.read%20tweet.write%20users.read&state=state&code_challenge=challenge&code_challenge_method=plain

the main difference are:

the first url puts plus signs between the scope.

the first url doesn't add response_type=code

the first url is the one created by power automate. If i try to add response_type=code to the power automate, it then adds a ? it does something like this

response_type=code?&

is there any way that i can just manually set these?

I've also tried with the http flow, i get the redirect but get a 302 error and the flow breaks there.

Is there any way to have the automate tools not insert plus signs between the scope variables and also how to get around the issue with the needed response_type=code?

Categories:

Connector development