Understanding the benefits of the 3 legged authorization I want to include this in my app.
However, I don't need the JS SDK for any other area of the App so I felt I could just simply set up a popup window that will pass the User onto the RC login screen to authenticate the app. However there is no clear instructions on what this request URL should be as all the examples include the JS SDK.
There was some explanation in the following PDF http://ringcentral.github.io/docs/RingCentral_OAuth-2.0_2015-10-08.pdf
that sort of hints that it should be a POST request.
So based on what I have read the URL should be (for testing)
https://platform.devtest.ringcentral.com/restapi/oauth/authorize
Then include, response_type, redirect_uri (which must match the App's Redirect URIs), client_id, and prompt.
https://platform.devtest.ringcentral.com/restapi/oauth/authorize?response_type=code&redirect_uri=<REDIRECT_URI>&client_id=<APP_KEY>&prompt=login_consent
I did this by GET method - which returns me to my RedirectURI with the following parameters attached the URL
&error=invalid_request&error_description=Parameter+[brandId]+is+invalid
Don't know if that is a response or what.
Then I tried it with POST method (as the PDF suggested that) and that returns with
Method Not Allowed.
What I did expect was the Login Screen as the blog post here describes ( https://blog.ringcentral.com/2015/10/ringcentral-announces-3-legged-authorization-to-simplify-login-...)
Any help would be much appreciated.
However, I don't need the JS SDK for any other area of the App so I felt I could just simply set up a popup window that will pass the User onto the RC login screen to authenticate the app. However there is no clear instructions on what this request URL should be as all the examples include the JS SDK.
There was some explanation in the following PDF http://ringcentral.github.io/docs/RingCentral_OAuth-2.0_2015-10-08.pdf
that sort of hints that it should be a POST request.
So based on what I have read the URL should be (for testing)
https://platform.devtest.ringcentral.com/restapi/oauth/authorize
Then include, response_type, redirect_uri (which must match the App's Redirect URIs), client_id, and prompt.
https://platform.devtest.ringcentral.com/restapi/oauth/authorize?response_type=code&redirect_uri=<REDIRECT_URI>&client_id=<APP_KEY>&prompt=login_consent
I did this by GET method - which returns me to my RedirectURI with the following parameters attached the URL
&error=invalid_request&error_description=Parameter+[brandId]+is+invalid
Don't know if that is a response or what.
Then I tried it with POST method (as the PDF suggested that) and that returns with
Method Not Allowed.
What I did expect was the Login Screen as the blog post here describes ( https://blog.ringcentral.com/2015/10/ringcentral-announces-3-legged-authorization-to-simplify-login-...)
Any help would be much appreciated.