Contributions
Re: OAuth 2.0
i am getting error using this URL. Invalid OAuth 2 parameters: https://developers.google.com/oauthplayground is not a valid Redirect URI. Do you want me to use 8819981768.apps.googleusercontent.com& as client id?? Client id and secret are automatically generated.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes7CommentsOAuth 2.0
I am trying to test OAuth using SOAP UI. The grant type-Client Credetials and resource owner password options work fine but when i try to change it to Authorization code or implict,I get Page could not be loaded issue. I think i do not have correct redirect URI that is having issue getting the access token from the authorization server. what URI should I use?6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes9CommentsRe: OAuth 2 get token - redirect URL
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. charlesfradleywrote: OK this is how it is fixed ... It is really nothingto do with Ready-API nor Soap-UI. On your authenticationserver there is a so-called "client profile" which has a redirect URL field, and that field can containanything, but whatever the field contains it needs to be identical to whatever you put inthe 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.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes0Comments