Authorising your application

We recommend different authorisation urls for desktop applications and web applications for desktop applications we recommend that for step “C” in the above diagram users are sent to:-

http://forums.cixonline.com/secure/authapp.aspx?oauth_token={request token from step “B”}&oauth_callback={optional address to redirect to on completion of autorisation}

Because this page resides inside CIX Forums users must be logged into CIX Forums before they can see this page. If they are not already logged in they will be asked to enter their user details before they are re-directed to the authorisation page. Because the oauth token sent in the link above will have been generated by your application with it's consumer key, the authorisation page is able to look up the details of your application and display them to the user for confirmation.

If you don't provide a callback url, the authorisation page will just ask the user to press the continue button within your application. Your application can then continue onto step “E”.

Once your application has recieved the access token's from step “F”, it should store them within your application for use in calling all subsequent functions from the CIX API.

For web applications we recommend using the CIX Mini sign-in form from within an IFrame. Therefore for step “C” your iframe would contain the page for this url:-

http://forums.cixonline.com/auth.aspx?oauth_token={request token from step “B”}&oauth_callback={this should be a url with your web application that breaks out of the iframe and continues to step “EE}

Once your application has recieved the access token's from step “F”, it should store them within your application for use in calling all subsequent functions from the CIX API.

OAuth Core 1 spec