Ask a Question

OAuth 2 get token - redirect URL

cotepatrice
Not applicable

OAuth 2 get token - redirect URL

Hi !

I try to get a token from my STS (which is Authorization Server by Thinktecture) to test against a ASP.NET MVC WEB API. I have all the values (endpoints, client ID, client secret, etc.) but one. What would be the redirect URL to use for your OAuth 2 Get Token method to work ? Maybe I’m missing something here, but I have no clue !

Note that when I get the token with a test client and copy / paste it in the box, it works. It’s just the Get Token Window that is not working. I get the login screen and the grant screen too, but the redirect has to point somewhere and I have no idea where.

Thanks !
6 REPLIES 6
SmartBear_Suppo
SmartBear Alumni (Retired)

Hi,

I believe you opened a support ticket for this? Am I correct?


Regards,
Marcus
SmartBear Support

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
charlesfradley
Contributor

 

we have the same problem here .... what is the solution ?

 

Thanks,

 

CFR.

 

Looking for the same information.  Specifically, what is the valid redirect url that will properly route the response back to SoapUi NG?

OK this is how it is fixed ...

 

It is really nothing to do with Ready-API nor Soap-UI.

 

On your authentication server there is a so-called "client profile" which has a redirect URL field, and that field can contain anything, but whatever the field contains it needs to be identical to whatever you put in the Oauth2.0 token request screen of Soap-UI.

 

At first this did not work for me because there was something set improperly elsewhere on the server.

 

So I had to do a real time session on voice with the system administrator, where I sent multiple Oauth 2.0 requests and he looked at the error messages in the logs on the server, and eventually he was able to figure out the incorrect settings.  I do not know the specifics of what he did.

 

Your mileage may vary.

 

Good luck in your quest !  It took me several weeks before we got to the the root cause of the problem.

 

 

bencross
New Contributor

I read the book in the link below and found that enabling MOCK HTTP LOG will allow you to get a access token using a URI of your choice if it is set up correctly

 

https://books.google.co.uk/books?id=QUXfBgAAQBAJ&pg=PA213&lpg=PA213&dq=soapui+redirect+uri&source=bl...

CV
Occasional Contributor

In my case, callback URI at authorization server matches with Redirect URI at SOAPUI, but i get a brwoser stating page cannot be loaded. what is going wrong? I have been stuck here for a long time and need help.


@charlesfradley wrote:

OK this is how it is fixed ...

 

It is really nothing to do with Ready-API nor Soap-UI.

 

On your authentication server there is a so-called "client profile" which has a redirect URL field, and that field can contain anything, but whatever the field contains it needs to be identical to whatever you put in the Oauth2.0 token request screen of Soap-UI.

 

At first this did not work for me because there was something set improperly elsewhere on the server.

 

So I had to do a real time session on voice with the system administrator, where I sent multiple Oauth 2.0 requests and he looked at the error messages in the logs on the server, and eventually he was able to figure out the incorrect settings.  I do not know the specifics of what he did.

 

Your mileage may vary.

 

Good luck in your quest !  It took me several weeks before we got to the the root cause of the problem.

 

 


 

cancel
Showing results for 
Search instead for 
Did you mean: