cancel
Showing results for 
Search instead for 
Did you mean: 

SSO

Former Member
0 Kudos

Hi Friends

what is the main differences b/w

sap logon ticket and user mapping in sso

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sunil,

I think the difference is SSO with user mapping requires user name and password while SSO with SAP logon ticket doesnot require user mapping if both portal and the backend system have same users. Any other ideas??

Regards

Harini S

Former Member
0 Kudos

Hi Harini

actually i have an idea abt sap logon ticket, in that the data is stored in the non persistent cookie. am i right?

other than that what is there in the sap logon ticket

at tha same time with user mapping we can forward the users logon data to others am i right? what is happening internally other than this.

please explain indetail abt these two

you are working for which company?

regards

Sunil

HCL

Former Member
0 Kudos

Hi Sunil,

You are right. SAP Logon ticket is stored as a cookie on the client and is sent with each request of that client. It can then be used by external applications to authenticate the portal user to those external applications without any further user logons being required. SAP logon ticket doesnot contain any password since passwords are not mapped. On the other hand, SSO done with user id and password needs more security since password is also sent across the network.

For more info, refer to these links. They will give u a clear idea about what is actually happening.

User mapping:

http://help.sap.com/saphelp_nw04/helpdata/en/f8/3b514ca29011d5bdeb006094191908/content.htm

SSO with user id and password:

http://help.sap.com/saphelp_nw2004s/helpdata/en/1c/22afe6b26011d5993800508b6b8b11/content.htm

SSO with SAP Logon ticket:

http://help.sap.com/saphelp_nw2004s/helpdata/en/89/6eb8e1af2f11d5993700508b6b8b11/content.htm

Hope this helps.

Regards

Harini S

Former Member
0 Kudos

Hi Sunil,

Follow the follwing steps -

1) Create a system by navigating to System Admin -> System Config -> Sytem Landscape

Select your folder -> Right Click -> New - >System

Follow this link -

http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/64b252473e9a479fcd275c79853620/frameset.htm

2) Create your system and now open the object for editing properties.

Enter the following properties - For example

Application host = 172.25.1.1

Gateway host = 172.25.1.1

Gateway service = sapgw00

Logon method = UIDPW

Remote host Type = 3

SAP Client = 200

SAP System ID = B47

SAP System Number = 00

Server Port = 3200

User Mapping Type = admin,user

3) Create a system alias for the system and Save

4) Now create a BW iview on the system created in the above steps.

Thanks,

Samta.

Answers (3)

Answers (3)

Former Member
0 Kudos

HI Sunil,

Check the links in my reply in the following thread,

<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=107666&messageID=1196791">SSO Scenarios</a>

Hope it helps.

Regards,

Vivek

Seems i have opened the thread for a long time

Message was edited by: Vivekanandan

Former Member
0 Kudos

Hi Sunil,

Following is the difference between two ways of SSO

1) In user mapping way user at-least has to enter his or her credentials at least once while in SAP Logon ticket it is not necessary.

2) For SAP logon ticket user-id on both(i.e portal and back-end ) servers shld be same while in user mapping type user-ids can be different.

In user mapping whenever users store their credentials, they are actually stored in database table and in turn ur iView will access the relevant data by using this table.

In SAP Logon Ticket , the ticket is issued by Portal Server for each successfull logged on user and it is stored as a non-persistent cookie in client browser.

This cookie contains user-id which is subsequently used for accessing back-end application.

For any clarifiacation plz revert back.

With Regards,

Amol.

Former Member
0 Kudos

hi,

Check out these links

and

Regards,

Srinath