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 on...
Forum Discussion
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.
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.
