We've been working to improve the experience while interacting with API BaaS. For customers, we've rolled out an updated portal that's integrated with Apigee's Single-Sign-On (SSO) service while the look and feel remains the same. The new portal is located at:
https://apibaas.apigee.com/apibaas
What does this mean for trial users ( trial/free API BaaS service using https://api.usergrid.com ) ?
At this time, trial customers using the free API BaaS service should continue to use its existing portal located at https://apigee.com/appservices. By January 2017, we will be releasing new trial infrastructure which takes advantage of this new portal, and will allow you to access all of your API BaaS organizations ( including trial ) using only the new portal.
What does this mean for customers?
When logging into the new portal at https://apibaas.apigee.com/apibaas, it will redirect you to Apigee's login page. Once successfully authenticated, you will be redirected back to https://apibaas.apigee.com/apibaas and can now access your API BaaS services.
Is there anything that I need to do?
Start accessing the API BaaS service by using the new portal URL( https://apibaas.apigee.com/apibaas) which includes updating your bookmarks. By September 30, 2016, all existing customer API BaaS portal URLs will redirect to the new location.
Are there any known issues to be aware of during the transition?
During the transition, you may experience the following error if you try to reset your password through the old API BaaS portal before the redirect has been configured:
"External SSO integration is enabled, admin users must reset passwords via provider: apigee"
This indicates that your BaaS cluster has been enabled to leverage Apigee SSO authentication in preparation to support the new API BaaS portal. Please switch to use the new portal located at https://apibaas.apigee.com/apibaas. It will redirect you to login with your Apigee account.
You may also experience one of the following errors upon logging into the the new portal if it has not yet been enabled to leverage Apigee SSO authentication:
"Unable to load organizations or you do not have access to any API BaaS organizations."
"Unable to authenticate OAuth credentials"
If this happens, please continue to use your old portal and check back after September 30, 2016.
Any API BaaS admin account or profile management will now be handled by the Apigee accounts service and not API BaaS directly. Please note that existing API BaaS access and permissions have been maintained during this transition. If you are experiencing any issues logging in or using the new portal, please contact Apigee Support.
Solution to Push Notification via cURL / Postman NPE
Live webcast on BaaS/Usergrid - Get to know more about Backend As A Service
Push notification patterns with BaaS
API Response Data Personalization Using BaaS
Tutorial: API BaaS Push Notifications
Unable to access API BaaS Orgs/Apps in Portal ( Apigee Cloud )