Skip to Content
Author's profile photo Ashutosh Rastogi

SAP Mobile BI – Import connection for X509 Certificate

Read me

SAP BI Mobile Server Single Sign On Support

SSO connections for Mobile BI ClientUsers do not create these connections manually, instead they can directly import these connections from the Configuration Server (MOBIServer)


  • Administrator can configure these connections at following location
    • Copy the from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
    • Then modify the file in custom folder
  • Choose your new connection identifier, say we choose ‘mysso‘. Add that to mobi.connections
    • mobi.connections=mysso
  • Choose a display name for your connection
    • mysso.DisplayName=Corporate_BI
  • For any SSO connection the first property that you need to enable is
    • mysso.BOBJ_MOBILE_SSO_ENABLED=true”
  • Configure CMS as follows (It should be noted that this value should match with <id>.aliases properties configured in at mobile server, else you will get MOB00902 error, null is not a valid authentication scheme)
  • Additionally following properties need to be configured
  • If you intend to perform single sign on via X509 certificate
    • mysso.BOBJ_MOBILE_SSO_TYPE=X509Certificate
  • If web application server that hosts mobile server, mandates incoming requests to have certificates
  • If web application server that hosts mobile server, does not mandate incoming requests to have certificates i.e. optional. If user denies to use the certificate User/Password would be the fall back option
  • Save the file

Now deploy the MOBIServer again after changes mentioned above. Once done, you can execute the following URL to check if the properties are configured correctly or not


In response, you should be seeing an XML with the configured properties as Key Value Pairs inside connection tag.

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.