Step by step procedure for SSO between EP 7.4 and ECC 6.0
Hi All,
This is my first blog in SCN,as part of ESS & MSS implementation we have implemented SSO between enterprise portal 7.4 and ECC 6.0.As everyone knows we have SSO is used to communicate with backend system without username&password.
Below is the procedure:
Step1 :Request the basis guys to set the following profile parameters in RZ10
ICM_Full_host_name = “basis guys give this url”;
Login/create_sso2_ticket = 2;
Login/accept_sso2_ticket =1;
After setting the profile parameters and don’t forget to remind the basis guys to restart the ECC server (if we didn’t restart the server the profile parameters will not reflect).
Step2: After Restart we have cross verify the parameters. Login to the SAP GUI with ECC credentials.
After Login to the ECC that just search for RZ10 t-code like below
In the RZ10 t-code select the Default profile(The profile parameters can be set in default or instance profile) and select the Extended maintenance and click on Display.
Then we have to check the profile parameters have been changed correctly or not.
Now everything in RZ10 t-code is perfect.
Step 3:To download the certificates we have to login to the NWA (you should have NWA role) as we don’t have Keystore Administration for the portal latest versions we have to use NWA .
(Its always preferred to delete the existing certificate and create the new certificate or u can download the certificate)
For creating the certificate:
Configuration–>Security–>Certificates and Keys–>Ticket Key Store–>View Entries–>Create New
While creating the certificate remember the name should be system name (Forex : epdev.apple.in:5000 , u have to create the name as epdev)
Now we have to login to the portal as NWA using http://server:port/nwa to download the certificate.
Configuration–>Security–>Certificates and Keys
Then you have to select the ticket keystore in the key storage.
Then select the SAPLogonticketpair-cert in the “View Entries” and click on Export Entryàselect the Base 64 type and click on Download
Then finally the certificate will downloaded like below
Step4: Login to the SAP GUI once again and search for “strustsso2” t-code and click enter
And click on the import certificate to import. Browse the certificate from the local pc and click on ok.
Then click on Add to Certificate List and add to ACL, An pop-up will display where you need to enter the Client as 000 and name as example “EPD”.
We have imported the portal certificate in the backend,now we have to get the backend into the portal.For that
Configuration–>Security–>Trusted Systems–>Add Trusted Systems
In the Add Trusted Systems select the By Querying System
If the bakend system is already maintained in the tech systems of SLD it will come in the list other wise you have to enter the following details and click on Next
Once you are done .The certificate will automatically added into the Certificate and keys list.
Then create the system object and test the SSO.
Done SSO is implemented successfully. In order to cross verify the ssois implemented correctly or not
Login to the portal àSystem Admin àSupportàAppl integrationàTest and configuration ToolàIn the Dropdown(right hand side)TransactionàRun
Then select the System Object and enter the T-code and click on Go,It should not ask for the username and password once again and iview should open.
check the below the link for reference.
SSO configuration between SAP Portal 7.3 and ECC 6.0 Ehp 6
Regards,
Anil
HI Anil,
Thanks for the documentation but I have few questions.
1. When you add ECC as trusted system in Portal in below screen what Client number you use? Is it 000 or something els.
2. What credentials you use here, Is it some specific admin credentials or I can use my personal credentials.
3. Now In step 1 & 2 I used client 000 and my personal credentials and found that certificate is visisble for ECC under keystore so thought this step is fine but when I tried to test my system object connection in system admin-> system landscape then I am getting the below error
Hi Anil,
Need some help in SSO .
1. In step 3, is it mandatory to create a new certificate. Can we use the existing one ?
2. IN adding backend as trusted system in portal in below screen kindly suggest.
a. Do we use client 000 or actual client number in below screen.
b. What user id password need to be used here. Is it something admin ID or my personal id with admin access is ok.
4. I have created the system but during testing i am getting the below screen. kindly suggest
Hi Shobhit,
Please use the Client number of the backend system whichever it is instead of 000. And we create a technical user for this configuration in your SAP system (check with basis), use that.
Also check if the your System has been defined in SLD or not. Check SLD is up or down & if its fine check the JCO connection (using ping and test).
Usually when you import the Portal Certificate to the respective backend system, and have created the SO, & if have followed the settings properly, this should be working. Go step wise and you would find the error.
Thanks,
Rakesh
Hi Rakesh,
Thanks, the issue get resolved. I added my actual backend client in trusted system. Tested the connection ok now. Also the ID I was using wasn;t powerful enough so used the special ID for this configuration which solves the issue. Thanks !
Thanks !
BR
Shobhit Taggar
Hi Anil It is very useful information Please keep posting these type of articles.
Much appreciated for your knowledge sharing.
Thanks
Krishna Teja
Good work Anil 🙂
Just wanted to add the below guide of some usual issues that we see here at Product Support.:
<http://scn.sap.com/community/netweaver-administrator/blog/2015/03/19/common-single-sign-on-j2ee-to-abap-issues-solutions-and-further-troubleshooting>
_ _ _ _ _ _ _ __ _ _
Kind Regards,
Hemanth
SAP Product Support
_ _ _ _ _ _ _ _ _ _ _
Join me online: http://scn.sap.com/people/hemanth.kumar/content
Nice Blog. Keep posting 🙂
@Anil i have used it to configure SSO FOR EP 7.5 with ERP 6.0.
Good Job
Dear Expert,
We have done migration of SAP EP Portal .After doing so we are facing issue As below
1.Login with Employee
2. Raise Leave Request through EP
3. After Checking the request it looks like Leave request got Created with User which is defined in RFC Destination .
SO Issue is that always Request getting created with BASIS User which is hardcoded in RFC Destnation
Thanks
Surekha