[Solved] Problem migrating from 17.3 hotfix E to 18.1 hotfix A with SAML/SSO active

Hello:

I just noticed a bug during the migration of our preproduction environment. Having SSO over SAML active on this environment, after migrating correctly everything without errors with engines/jboss, when we tried to access to appian (it didn't matter which url) I throwed error 500 (couldn't log-in). Also, if we tried to go to the portal login (to login with admin user that is outside of the SSO login rules) using <domain>/suite/portal/login.jsp it throwed 403. Looking at the logs I saw this errors refering the first one to a "normal" SSO log-in try and the second one to the portal log-in:

  1. 14:47:52,898 INFO [stdout] (http-0.0.0.0:8443-1) 2018-04-11 14:47:52,892 [http-0.0.0.0:8443-1] ERROR com.appiancorp.security.authz.Forbidden - Error getting user details for authz logging. Proceeding to log with empty user details: java.lang.NullPointerException
  2. Null value was assigned to a property of primitive type setter of com.appiancorp.security.auth.saml.service.SamlSettings.rememberIdp.

As you can see in the screenshots attached, there is a new column ( remember_idp ) in the saml_config table in 18.1 that wasn't in 17.3. It was set to NULL by default, causing the NullPointerException in both cases. After setting it to 1, It worked flawlessly. 

 

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data