Using the adminFallback=true via the REST API is not working

« Go Back


EnvironmentProduct: Rollbase Private Cloud
Question/Problem Description
Using the adminFallback=true via the REST API is not working. We do API updates for data, so this is the URL we are testing with:
I want to use the API Service account via the old password method, even though regular users will utilize SSO. This password was the same as before SSO was enabled.
Is the URL wrong? Is there another issue?
Steps to Reproduce
Clarifying Information
The tenant has SAML authentication enabled.
Error MessageSession expired or invalid login credentials
Defect/Enhancement Number
Yes, the URL is wrong.

First, is necessary to authenticate using the login API:

<resp status="ok">

Warning: The method getDataObj is deprecated. Please change any existing code to use getRecord.

Second, using the returned sessionId run the subsequent calls (replacing sessionId, xxx, yyy and zzz):
The way to call REST API directly is using Basic Authentication.
Examples can be found accessing Application Setup > Code Generator

See the Notes section for more information.
Last Modified Date2/17/2017 6:25 PM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful.

Characters Remaining: 255