SAP Knowledge Base Article - Preview

3349843 - After upgrading from BI 4.2 to 4.3 SAML SSO stopped working and getting HTTP error


  • You have upgraded from a major BI version (ie. 4.2 to 4.3)
  • You have copied over previous SAML configuration files such as (idp-meta-downloaded.xml, securityContext.xml, content in tomcat custom directory such as .properties files)
  • You have copied over contents from <BOBJ INSTALL DIR>\tomcat\webapps\BOE\WEB-INF\config\custom into your new BI 4.3 deployment
  • CMC and BILP logon pages do not load
  • Getting HTTP 404, HTTP 500, HTTP 403 errors when accessing CMC/BILP
  • SAML SSO worked previously in BI 4.2 but now does not work in BI 4.3



BI 4.2

BI 4.3



SSO, SAML, AUT, AUTH, Authentication, HTTP, error, status code, 404, 500, 502, 403, 400, CMC, BILP, Fiori, logon, page, login, upgrade, update, patch, 4.2, 4.3, BI, BOBJ, BOE, securityContext.xml, entityBaseURL, keystore, csrf, invalid, for, Invalid CSRF token found for, Responding with 403 status code , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.