Migration to SAP BO 4.0

[Former Member]

Hi,

I am migrating my application from SAP BO 3.x to SAP BO 4.0 and everything is fine except the migration of the Java BO SDK part. I am unable to migrate the SSO logic. In the previous version I used TrustedPrincipal.conf file, but it seems that in SAP BO 4.0 I can not use it anymore.

What are the necessary steps by the implementation of SSO in SAP BO 4.0 and is there any way to migrate my Java logic from the previous version without the necessity to create and diploy a new WAR file. Please advise.

Thank you vey much!

[Former Member]

Hi May,

Firstly, you need to set up trusted authentication in BI 4.0 environment.

This activity requires you to have an account with administrative rights that can log on to the Central Management Console (CMC).

Below are the steps to set up a shared secret on the CMS that will be used to establish trust with your custom application;

1. Log on to the CMC with administrative rights.

2. Go to the Authentication management area.

3. Click the Enterprise option. The "Enterprise" dialog-box opens.

4. Scroll down until you see "Trusted Authentication".

          a. Click Trusted Authentication is enabled.

          b. Click New Shared Secret. The following message is displayed:

        Shared secret key is generated and ready for download

  c. Click Download Shared Secret. 

      Note: The shared secret is used by the web server and the CMS to establish trust.

      The "File Download" dialog opens.

  d. Click "Save" and point to following directory to save the TrustedPrincipal.conf file:

               <INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\win32_x86

  e. To specify the number of days that your shared secret will be valid, enter a value for the "Shared          Secret Validity Period" field.

   f. Specify a timeout value for your trusted authentication requests.

     Note: The timeout value is the maximum amount of time, in milliseconds, that the clock on the      client and clock and the CMS can differ. If you enter 0, the amount of time the two clock times      can differ is unlimited. It is not recommended you set this value to 0 as this may increase your      vulnerability to replay attacks.

5.Click Update to commit the shared secret.

Once trusted authentication is configured in the            Central Management Console (CMC) , you can use the  ISessionMgr interface to pass the trusted user name and the shared secret and then log on            to the CMS.

ISessionMgr sessionMgr = CrystalEnterprise.getSessionMgr();

ITrustedPrincipal trustedPrincipal = sessionMgr.createTrustedPrincipal("userName", "<cms>:<port>", "sharedSecret");

IEnterpriseSession enterpriseSession = sessionMgr.logon(trustedPrincipal);

Hope it helps.

Regards,

Anchal

[Former Member]

Hi Anchal,

Thank you very much for the detailed explanations!

I will try to configure it according to the given steps, thank you again!

Best regards, have a nice day,

May

[DellSC]

Please see my response to your original post here:  http://scn.sap.com/thread/3407604

-Dell