If you want to setup client side SNC for Business object 4.0, you will have to check the configuration in BI 4.0 is precisely an equivalent as XI 3.1 or it hasn’t modified. Any Alias i.e. enterprise, LDAP, Win AD will be able to impersonate the SAP alias related to that account once the system is designed. Please remember the way you are having with the analysis for workplace is that the expected till version four.1. At last you have to check out the KBA. Anyhow, users ought to be able to use their LDAP username within the client tool as long as you have got a STS configured.
Security Token Services (STS) are being introduced by SAP BO BI4.0 as new service. The tokens that is being issued proprietary by STS is known to be as Assertion Tickets. Then you have to make simple call by using Bi4.0 SDK client that desires SSO2DB to an SAP BW system. Now the call is being processed by STS .Which might return as Assertion ticket valid for logon to the target SAPBW system if the user had associate alias that mapped to system. Now by using the Assertion Ticket as a credential the BI4.0 client would be connect directly to SAP BW system via RFC.
The following steps are mentioned below to use single sign–on to the SAP system by Utilizing Security Token service:
- You have to produce key store and certificate for SAPBO BI4.0.
- Now you have to import SAP BO BI 4.0 certificate into SAP BW.
- Next you have to Setup SAP SSO Service in SAP BO 4.0 CMC.
- Finally you have Setup of SSO against SAP BW for SAP BO BI 4.0 BICS or JCO connections
By following all these steps you can easily create a client side SNC for business objects.