Readme

SAP BI Mobile Server Single Sign On Support


Prerequisites

  • SAP Business Objects BI platform configured for SAP authentication.
  • SAP systems configured to generate SAP Logon tickets
  • A form based URL (such as the SAP portal) to log on and generate the required MYSAPSSO2 cookie


First step

is to enable the Authentication Scheme

  • Copy the authscheme.properties from default folder in to custom folder (<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config)
  • Then modify the authscheme.properties file in custom folder
  • Un-comment line ‘MYSAPSSO2=com.businessobjects.mobilebi.server.logon.impl.MySapSSO2’
  • Save and close the file


Second Step

is to define the default SSO configuration

  • Copy the sso.properties from default folder in to custom folder (<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config)
  • Then modify the sso.properties file in custom folder
  • Choose your default CMS identifier
    • default.cms.identifier=abc
  • Now define your authentication scheme (the one that you have enabled in first step)
    • abc.authentication.scheme=MYSAPSSO2
  • CMS can be provided as an Alias, IP or cluster name
    • Alias
      • abc.aliases=boe.xyz.corp:6400
    • IP
      • abc.aliases=10.10.10.10:6400
    • Cluster name
      • abc.aliases=@xyz
  • Now configure all the properties using this identifier as below
    • abc.sap.sid=XYZ
    • abc.sap.client=200
    • abc.authentication.type=secSAPR3
    • abc.cookie.name=MYSAPSSO2
    • abc.product.locale=en_GB
    • abc.preferred.viewing.locale=en_GB
  • Save the sso.properties file.

Third Step

is to now deploy the MobileBIService again after changes mentioned above. Once done, you can validate if your SSO has been setup correctly by executing following URL from browser

http://<server>:<port>/MobileBIService/MessageHandlerServlet?message=CredentialsMessage&requestSrc=ipad&data=<logon logonViaSSO=”true”/>

Note: While executing the URL in browser, you should be sending a valid MYSAPSSO2 cookie with it.



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

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Florian Georg Furtmüller

    Hi, what about CMS in a clustered environment, should we use then:

    abc.aliases=boe01.xyz.corp:6400,boe02.xyz.corp:6400

    because of the naming of the parameter .aliases, is this a comma separated list or do we have to use just space?

    Thank you

    (0) 
      1. Florian Georg Furtmüller

        thats true and is also specified in your article above, the problem what we are facing is that during System installation we did not define any @clustername the system also did not require to specify any @clustername? Regards, Florian

        (0) 
        1. Vikas Kumar Yadav

          Hi Florian,

          when you say clustered do you not mean CMS are clustered, I mean sessions, files stores etc are not shared between the BOE systems? or it is just a windows cluster.

          Regards

          Vikas

          (0) 
          1. Florian Georg Furtmüller

            Hi Vikas,

            Okay, I verified BOE system configuration with our basis team and we figured out that CMS has been installed on node 01, node 02 is operating with remote CMS of node 01, so in that case our ‘clustered’ CMS is from node 01, which means DB and file systems are shard via Windows Cluster. We applied changes on our sso.properties file and it seems that its operating as expected now – thank you for your hints and replies!

            Best wishes, Florian

            (0) 

Leave a Reply