Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > FAQs > 403 Forbidden error using API after migration to UCP

403 Forbidden error using API after migration to UCP

Table of Contents


After migration to the UCP (unified cloud platform) the major change for most customers is the endpoint url changes for leveraging the API on the UCP platform.  There however was a change some may encounter if basic auth was being used while on our LCP (legacy cloud platform).  Basic auth was EOS (end of support)  on 10-27-2011 but would have still been functional for accounts if they were both older then that date and associated to a premium account.  With UCP basic auth is officially EOL (end of life) and the attempt to do basic auth will result in 403 forbidden errors.


With basic auth, you're passing the username/password in the headers for each request, rather than an API call which exchanges your username/password for a token once.  You will need to do session based authentication on the UCP platform.

You must to post a comment.
Last modified
15:29, 29 May 2014


This page has no custom tags.


This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.