SSO to BSP using NTLM with application parameters

[Former Member]

Hi all,

As part of the CRM activity, the customer's system sends out an email to a user with a link pointing to a bsp. Part of the url is the call id which the bsp needs to display.

The customer does not wish for the users to input user/pass when accessing the bsp.

According to documentation, NetWeaver supports only SAP logon tickets and X.509 SSO methods(http://help.sap.com/saphelp_nw04/helpdata/en/02/

d4d53aa8a9324de10000000a114084/ content htm).

Found this thread that suggest a workaround:

Seems like it should work, but ITS forwards to a static URL.

Any ideas on how I can make sure that after the whole sso process is complete, the bsp will still remember which call-id it needs to display?

Regards,

Eric

[Former Member · Accepted solution]

If you want you can put the user name and password in the ICF service for the BSP application. This works if this BSP application is meant for everyone.

on the other hand since this is a BSP application and it is going run in the browser, I believe if user has the digital certificate in his/her browser (similar to what SAP gives you for OSS or SDN) then you don't need to provide user/passwd.

-Sanjeev

[Former Member · Accepted solution]

The goal is to have the changes made inside the bsp recorded to the logged in user. So one user for all is not applicable.

After fiddlig around with the forwarding settings and the ITS, I managed to get this thing working. Almost.

When I access the BSP url, it gets forwarded to and from the ITS and I get a SSO2 ticket. However, when it comes back from the ITS I get a http 404 error page. If I refresh that page, the BSP loads fine, with the transferred parameters and the correct user.

Can't get my head around why it gives me a 404.

Eric

Message was edited by: Eric Labiner