need to create SSO2 ticket via java

[#1]

I need to write an iview, that issues a new SS02-ticket before the different SAP system (SRM, ITS) are called.

Is there a how-to or something else, which describes the programmatic creation of an SSO2 ticket?

Background: The customer has a variety of SAP system, and in every system, the user has a different SAP ID.

I tried SSO2 with reference system and user mapping, but obviously EP requires a 1:1 relation. (Portal User A maps to user B in all SAP systems via reference system).

[holger_stumm2]

The regular SSO-setup works fine. Portal user is mapped to reference system user (HR-Username).

If the SRM-username is equal to the HR-username, everything is fine as well. SSO works.

But what if the SRM-user has a different name?

Can you elaborate on the User Mapping question? Somebody from SAP mentioned to me, that some customer are doing remapping, but not, where to do it.

Where would I re-map the SAPSSO2 user to the SAP SRM-user? Is it in the SRM target system with something like STRUSTSSO2? or SU01? .

Thanks

Holger

[achim_hauck2]

Holger,

in the portal, go to "system administration / system configuration / system landscpae" and edit the "User Management" properties of your SRM system like this:

User Mapping Type: "admin, user" (whether the mapping should be done by the admin, by the user or both of them)

after that you have the option to map your user for the SRM system at "user Administration / User mapping"

kr, achim

[holger_stumm2]

Yes, I already did that.

But the SSO-Ticket is always for the HR-username (Reference System) , and when I call the SRM-System, even with the mapping, the SSO-tickets alway is the same, issued for the reference system user.

The user is denied, because the SRM-username is not the same as in the HR-system

[achim_hauck2]

that sounds like a misconfiguration. the mapped user should be written in the ticket (http://help.sap.com/saphelp_nw2004s/helpdata/de/fe/d22a41b108f523e10000000a155106/frameset.htm)

are you sure, it's the wrong useridin the ticket? did you try whether the whole SRM-SSO is configured correct by using a portal user thats userid is the sam as in the SRM?

kr, achim