SSO Problem (I give out points!!!)

[Former Member]

We configured SSO in the portal EP6.0 SP10 to a CRM 4.0 server using STRUSTSSO2. The portal verify.der file was uploaded and the EP server was added to the ACL fine.

When I create an SAP transaction iview in the portal, it works great. When I try to connect using an BSP iview, the single signon does not work. I get a network logon popup one time.

Please advise if you have any ideas on what it might be.

The user exists in CRM with SAP_ALL permission.

Thank you.

Tom

[Former Member · Accepted solution]

In case of BSP, it uses WebAS properties of the system definition to connect to SAP R/3. Make sure you have the BSP properties set right.

There is also a way to debug BSP iview.

Make sure authentication scheme in the iview is set to default.

Make sure Iview propety Content - BSP following properties are set right.

Application Namespace - SAP

BSP Definition type - BSP

Business Server Page Application - give the BSp name here

Customer Name Space - SAP

Start Page - what ever

System - Your system alias.

You can also debug your BSP application from Portal very well.

Here is path.

Logon to Portal --> System Administration -->Support -->SAP Application --> Select BSP and run

It gives all the options.

I hope this helps.

[Former Member]

Hi Thomas,

Were you able to fix your problem. I am having the same problem. SSO works with transaction iview but doesn't work with BSPs in CRM. thank you.

[Former Member]

Prakash,

Do the SM50 trace, your error may be the same but your problem might be different - the trace will tell you.

Nick

[Former Member]

Hi Nicholas,

Thank you for your reply. I solved it. I wasn't login in my portal with it's fully qualified name.

Prakash

Message was edited by: Prakash Singh

[Former Member]

1st make sure the cookies are actually passed, and make sure the BSP runs in the client you configured SSO for.

2nd you can trace things on the ABAP side.

Create an SM50 trace with only the security component turned to trace level 2. In order to do so, run transaction SM50 and select some of the dialog work processes (around 5). Then choose 'Processes -> Trace -> Active components' from the menu or use CTRL-SHIFT-F7). Set the trace level to 2 and select only the 'Security' component. Reproduce the SSO problem, and note the time. Return to the SAP system to check the traces you just started (CTRL-SHIFT-F8 in SM50). This trace collects

information on work process level. Therefore, you need to find the work process that has handled the authentication attempt.

This procedure is described in Note 495911 in more detail

Nick