cancel
Showing results for 
Search instead for 
Did you mean: 

SSO configuration steps

08-18-2008 10:13 AM
1081 views 14 comments
0 Likes
SAP Managed Tags
Subscribe

Hi All,

Let me know what are the minimum steps required for SSO configuration so to access Transaction iviews from portal .

I have some documents , but those also include SSO with BI . But I want to do SSO only to ECC .

Regards,

Surya

0 Likes

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Likes

For SSO with ECC and portal read this blog...

and for SSO with BI and Portal read this blog..

hope it helps !!

Former Member
0 Likes

Has this resolved your issue or no...?

If not what is the problem you have at this point of time?

Regards,

Mahantesh

Former Member
0 Likes

Thanks All

Former Member
0 Likes

Surya,

steps given by GLM, are sufficient for SSO.

Just check the dates when exporting the certificates and the user names in java stack and ABAP stack i.e Portal and R/3 must be same.

The other simplest way is to go for SSO with user mapping which doesn't require these exporting of certificates and you don need to have same user name also. Let me know if you eed any more info on this.

Regards,

Yogesh...

Former Member
0 Likes

Thanks for reply ,

And anyhave usermapping is not suggested and not going for that.

Regards,

Surya

Former Member
0 Likes

Adding to GLM's reply...

you also need to assign Issuing systems credentials to the ACL list of the recieving system in transaction STRUSTSSO2. The values can be derived from login.ticket_issuer and login.ticket_client parameters in UME propertysheet in config tool.

Thanks,

Deepa

Former Member
0 Likes

Hi Deepa,

I think this is not essential ..

Anybody can judge on her answer.....? to avoid confusion .

Regards,

surya

former_member110461
Active Contributor
0 Likes

Deepa is correct.

The wiki is at the top (next to the forums link). From there go into portal.

Or just go straight to here:

https://wiki.sdn.sap.com/wiki/x/vik

Paul

Former Member
0 Likes

Hi Surya,

Thanks for your reply. You do need to maintain ticket issuing server in the recievers ACL, which will be used by the reciever systm later to validate if a trusted Portal server issued the logon ticket.

Thanks,

Deepa

Former Member
0 Likes

Hi,

A.Single Sign-On using SAP logon tickets without user mapping

1)Users must have the same user IDs in all SAP systems that are accessed via SSO with SAP logon tickets.

2) If the SAP user IDs are the same as the portal user IDs, user mapping is not required. You need to perform the following steps:

a) Configure Portal Server for SSO with SAP Logon Tickets

b) Configure SAP Systems to Accept and Verify SAP Logon Tickets

B: Single Sign-On using SAP logon tickets with user mapping

If users have different users IDs in the SAP Systems than in the portal, you must define a SAP reference system and map each user's user ID to their user ID in the reference system.

You must perform the following steps:

1.Define an SAP Reference System for User Data

2. Configure Portal Server for SSO with SAP Logon Tickets

3. Configure SAP Systems to Accept and Verify SAP Logon Tickets

SAP logon tickets contain information about the authenticated user. They do not contain any passwords.

logon tickets contain the following items:

u2022 Portal user ID and one mapped user ID for external applications

u2022 Authentication scheme

u2022 Validity period

u2022 Information identifying the issuing system

u2022 Digital signature

Procedure

1) Download verify.der from keystore of the portal

2)Upload verify.der in Tran: STRUSTSSO2

3) Check that the following instance profile parameters are active

login/accept_sso2_ticket is 1

login/create_sso2_ticket is 0

Points Are Welcome

Thanks

SubbaRao Chinta

Former Member
0 Likes

1) Export the J2EE signing certificate to Cluster-> Server -> Services->Key Storage->Runtime->

TicketKeystore->SAPLogonTicketKeypair–cert. (or you can download the certificate by logging on as System Admin role and then System Admin tab ->System Config->Key Store...certificate name is verify.der) Then I imported this file successfully into R/3 (ECC 6.0) using STRUSTSSO2.

2) Set the profile parameter login/accept_sso2_ticket to the value 1 in every instance profile

3) Also set the fully qualified domain name of the server in transaction RZ10

Thanks,

GLM

Former Member
0 Likes

Hi,

Thanks for your reply ,

Is these three steps are suffient????

Or anyother things are needed , I Will check and close the thread..

Regards,

Surya

former_member110461
Active Contributor
0 Likes

Surya,

As the sticky says, read the WIKI, there is lots of information in there.

Paul

Former Member
0 Likes

WIKI?????????