Please try using "login consent" pair for now or just do not pass this parameter at all. Our implementation is not 100% compatible with other vendors OAuth implementation, we are fixing it next release.
I can try removing the parameter and see if that works, but in my experience APIs throw-error when you leave off required parameters.
Also, as an alternative, what do you mean by "use "login consent" pair for now?"
"prompt" is not a required parameter, as far as I know.
I mean specifying "prompt=login%20consent" also helps.
In your example it probably means:
<cfhttpparam type="url" name="prompt" value="login consent">
Thanks for the help.
Ok. I tried both and I get the same error. So, I removed it as you suggested and changes happened.
Now, it's redirecting me as follows:
https://www.MYSERVER.com/login/unifiedLogin.html?session=-XXXXXXXXXXXXXX&6597080091492620690&responseType=code&clientId=MYCLIENTID&brandId=BRANDID&state=rct7dor1i5479Le8n2ca4e5xLt3dv0d6kn4hug23nnn3tckua0&localeId=en_US&endpointId=&display=page&prompt=login%20consent%20sso&scope=&appUrlScheme=https%3A%2F%2Fwww.MYDOMAIN.com%2Fsubprocesses%2Fringcentral%2FringCentral_callback.cfm&ui_options=&hideNavigationBar=true
Obviously, it's throwing a 404 error because it's trying to get this path is not on my server.
It appears to be attempting to allow me to login, but for whatever reason it's trying to run the path off of my server.
The first request to
https://platform.devtest.ringcentral.com should redirect you first to login form which is (if I am not mistaken) is on service.devtest.ringcentral.com or login.devtest.ringcentral.com host. So if you see this kind of redirect it is a correct one - it should bring login form to your browser.
That's what I thought, but it isn't prompting me with the login form...it's trying to use the path off my server as opposed to Ringcentral's server. I know this process works, because I have authorization working on Google's API...
This is pretty strange. Looks that some party intercepts the redirect and substitutes the host name with your server name. Actually authorization code flow should be initiated from browser JS in your case to work properly (since you suppose to get a redirect directly to browser). If this first call is actually initiated by your backend it will not work (unless your backend passes the full redirect URI to a browser client somehow).
I am initiating it from my backend server. That website domain is my website that is being replaced.
I know with Google Authorization Flow, it brings up Google's page, I login, it passes it to my redirect URI which grabs the access tokens and refresh tokens from the JSON string that is passed and I am on my way. It should work the same....
Are you saying you can't initiate the authorization flow from the backend (I know others have with PHP which means CF should be able to do it) or are you saying in my case I must use JS? I would like to avoid JS.
When you say my backend must pass the full redirect URI to the browser client, I am not following you....I can pretty much do anything with CF, but if you are saying that the authorization flow must be on the client side, then it can't be done.
I am not sure the process is correct. Please read the 4-steps guide here:
https://github.com/tylerlong/ringcentral-python#authorization-code-flow-3-legged-authorization-flowSo for step #1, what is the uri in your case?
It's here and defined above in code like this:
<cfset redirect_uri = "MYREDIRECTURI.com" />
<cfhttpparam type="url" name="redirect_uri" value="#redirect_uri#">
I don't think that's the issue....
It's been a week. I appreciate the help from some of you on this forum, however, Ringcentral's lack of response from the Developer team is disappointing.
I have used this code with Google's API and it works, so I know my authorization flow works with them...
I will add something else....Tyler's favorite answer to everyone is to point people to your code examples...why not spend a little time and let's get a working CF example for folks...believe me...there are a lot of applications out there that use CF.
Jason, regarding your questions:
1) Yes, your URL is correct
2) Here is the call I made and traced for your reference. So you can see that our server returns full URL in the path.
GET https://platform.devtest.ringcentral.com/restapi/oauth/authorize? client_id=...&redirect_uri=...&response_type=code&state=... HTTP/1.1 Accept-Encoding: gzip,deflate Host: platform.devtest.ringcentral.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
HTTP/1.1 302 Found Server: nginx/1.10.2 Date: Mon, 12 Mar 2018 20:02:45 GMT Content-Length: 0 Connection: keep-alive X-Application-Context: application:8080 Location: https://service.devtest.ringcentral.com/mobile/loginDispatcher? responseType=code&clientId=...&brandId=1210&state=...&localeId=en_US& endpointId=&session=-2915783893910517926&display=page& prompt=login%20consent%20sso&scope=& appUrlScheme=...&ui_options=&hideNavigationBar=true
I pointed you earlier to this post:
http://www.codersrevolution.com/blog/CFHTTP-doesnt-resolve-URLs-properly-on-redirect. So maybe you need to check with ColdFusion support.
