Changes to Non-SAML SSO Site Behavior

« Go Back


EnvironmentProduct: Rollbase Private Cloud
Question/Problem Description
Previously, we had a customer site using SSO (HTTP POST). While this was enabled (and working for over a year), the site still allowed password-based login. After 4.4, this stopped working and the HTTP POST enabled site, exhibits the same behavior as a SAML enable site (can't login with old style RB password, support must use super admin or login as functions in order to login to site to provide support.)

What changed here and is this intended?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
In Rollbase version 4.4, the way Rollbase handles fallback for an authentication failure has changed.
There is a documentation section "Change to authentication fallback behavior", where it specifies a new url parameter "adminFallback" which should be set to use password based login.
This is applicable only for Admin's (like before) and the only change is that this now does not happen automatically.

See the Notes section for more information.
Last Modified Date2/17/2017 5:46 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