BO SSO with the SAP front end tool

Question

Hi ,
I am trying to go with SSO in the BO 3.0 version but i an facing an error when i am trying to create the ticket .... i am pasting the error and the architecture  of the process kindly help me in this issue....
Please can we have SSO setup in the following envioronments and applications
BO Systems : B0S/B0D/B0Q/B0P
EP Systems: S0E/D0E/Q0E/P0E
Applications: InfoViewApp /CmcApp
This is required for complete implementation of  Business Objects security model because SAP users do not have passwords
Problem Description: (Precise description of problem)
Setup SSO in the following environments and applications :
BO Systems : B0S/B0D/B0Q/B0P
EP Systems: S0E/D0E/Q0E/P0E
Applications: InfoViewApp /CmcApp
This is required for complete implementation of Business Objects security model because SAP users do not have passwords
Analysis:
SAP side u2013 items already complete:
- on the SAP side the portal needs to generate tickets for the BI system
- the BI system needs to trust the Portal
- the BI system needs to accept SSO tickets
- all the machines need to be in the same domain
Installation of the complete items can be confirmed by the presents of portal login ticket at these addresses :
Several issues needs to be checked in the Business Objects environment:
- the SAP authentication needs to be configured for the SAP system
- the web.xml for InfoView needs to use secSAPR3 as default setting for the authentication
- the default system in the SAP authentication options should be configured to use your SAP BI system
- the Business Objects system needs to be in the same domain
Analysis of authorization requirements (Mandatory for programs and tables):
Solution: (Final solution)
To complete the SSO implementation in the SAP BO environment, these issues should be completed:
1):  Test that the SAP portals actually accepts portal login tickets:
https://epproduction-app.statoil.no/irj/portal
https://epquality-app.statoil.no/irj/portal
https://epdevelopment-app.statoil.no/irj/portal
https://epsandbox-app.statoil.no:56201/irj/portal
2):  Implement and test the following items:
- the SAP authentication needs to be configured for the SAP system
- the web.xml for InfoView needs to use secSAPR3 as default setting for the authentication
- the default system in the SAP authentication options should be configured to use your SAP BI system
- the Business Objects system needs to be in the same domain
3): Check that fully qualified URLu2019s for BO systems calls the sso login:
- This also should be tested and confirmed working by the basis team (EDB) before the task is completed
- Comparison with production setup today is required
- Fully operational SSO setup in Prod can be found at:  http://boxi.statoil.no:8080/InfoViewApp/logon.jsp
Tomcat implementation
SSO setup implicates these reconfiguration elements:
-     Update of web.xml for InfoViewApp and CmcApp in Tomcat :
This is the correct web.xml setup for SSO (gathered from prod env.):
    <!-- Choose whether to let the user change the CMS name -->
    <!-- If it isn't shown the default System from above will be used -->
    <context-param>
        <param-name>cms.visible</param-name>
        <param-value>true</param-value>
    </context-param>
    <!-- You can specify the default Authentication types here -->
    <!-- secEnterprise, secLDAP, secWinAD, secSAPR3 -->
    <context-param>
        <param-name>authentication.default</param-name>
        <param-value>secSAPR3</param-value>
    </context-param>
    <!-- Choose whether to let the user change the authentication type -->
    <!-- If it isn't shown the default authentication type from above will be used -->
    <context-param>
        <param-name>authentication.visible</param-name>
        <param-value>true</param-value>
    </context-param>
    <!-- The default home page -->
    <context-param>
        <param-name>homepage.default</param-name>
        <param-value>/jsp/listing/home.jsp</param-value>
    </context-param>
    <!-- If the locale preference is disabled (only english languages will be used/allowed) -->
    <context-param>
        <param-name>disable.locale.preference</param-name>
        <param-value>false</param-value>
    </context-param>
    <!-- Set to false to disable Siteminder single sign on. -->
    <context-param>
        <param-name>siteminder.enabled</param-name>
        <param-value>false</param-value>
    </context-param>
    <!-- You can specify the siteminder Authentication type here -->
    <!-- secLDAP, secWinAD -->
    <context-param>
        <param-name>siteminder.authentication</param-name>
        <param-value>secLDAP</param-value>
    </context-param>
    <!-- Set to true to enable Vintela single sign on. -->
    <context-param>
        <param-name>vintela.enabled</param-name>
        <param-value>false</param-value>
    </context-param>
    <!-- Set to true to enable other single sign on. -->
    <context-param>
        <param-name>sso.enabled</param-name>
        <param-value>true</param-value>
    </context-param>
    <!-- Set to false to disable logon with token. -->
    <context-param>
        <param-name>logontoken.enabled</param-name>
        <param-value>true</param-value>
    </context-param>
    <!-- For turning persistent cookies on/off for the logon page.  Defaults to true if this is not present -->
    <context-param>
        <param-name>persistentcookies.enabled</param-name>
        <param-value>true</param-value>
    </context-param>
Kerberos setup:
Please see separate attached document in C148946.
Implementation plan
1)    Implement SSO on Sandbox server st-tw283, and test in cooperation with Migration BO project and Solution Responsible
2)    Implement SSO on Dev server st-w1024, and test in cooperation with Migration BO project and Solution Responsible
3)    Implement SSO on clustered servers Q server st-w1023 and Sanbox server st-tw63, and test in cooperation with Migration BO project and Solution Responsible
4)    When approved by test group, finish test approval doc and prepare for production environment implementation
can any one guide me in this since this is critical and if any documents are there pls. forward me i will check them
Thanks & Regards
Sanjeevkumar.D.Belagal
09900084312

Answer 1

Hi Sanjeev,
It is kind of very hard to go through all the details you have written.
You have BO 3.0 and SAP in Back End.
First you have to install BOBJ
Then install Integration Kit.
Then you have to take some steps in SAP BI side such as creating RFC.
Then you will import your roles into BOBJ by going to CMC.
After that one you will be able to attain SSO.
Have you done all? If yes then exactly what error or issue you are getting? Be brief please.
When you mention any problem mention following.
What version you have?
What is in the back end?
What service Pack and Fix Pack you installed?
What environment you have?
What error you are getting and on which step?
Regards,
Bashir Awan