Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

BO SSO (SNC) is not working in InfoView

Hi Gurus,

We are facing a very strange scenario in our Production environment.

The BO SSO (SNC) is working fine in Dev and QA. The problem is in Production (clustered environment).

The details are following:

The SIA is running in 3 different servers (for load balance): Server1 (our CORE server), Server2, and Server3

CMS is running only in Server1, it has been stopped in Server2 and Server3.

Also we have 4 WebI Processing Servers in each server (4 x 3 = 12). Like below:

Server1.WebI Processing Server

Server1.WebI Processing Server1

...

Server2.WebI Processing Server

Server2.WebI Processing Server1

...

Server3.WebI Processing Server

Server3.WebI Processing Server1

...

The TOMCAT is running in a separate server (Server4). It is pointing to Server1 since CMS is in Server1.

SNC configuration steps are following:

1. Generated BO certificate (BO.crt) in all three BO servers. Ie., BO.crt is available in all 3 servers.

2. Imported the BO certificate in SAP. Then generated SAP certificate (SAP.crt).

3. Imported the SAP certificate in all 3 BO servers.

4. Provided SSO credential for domain user in all 3 servers. [Domain user is same in all 3 servers]

5. In CMC  SAP filled the Entitlement system, SNC, Options.

6. Imported the SAP users.

7. Aliased the WindowsAD users to SAP Roles.

Scenario 1:

1. Logged in to Designer via SAP Authentication with user id USER1. Created a new test universe (Universe1) with option u2018Use single sign-on...u2019

Universe is working fine. Exported it to repository.

2. Logged into InfoView via WindowsAD with user id USER1.

Created a test report (Report1) from the SSO universe. Report is working fine.

Saved the report into the public folder.

3. Logged into InfoView via WindowsAD with user id USER2.

Refreshed the saved report. But itu2019s throwing the error message u201CUnable to connect to SAP BW server Incomplete logon datau201D

Created a new report from the SSO universe, but same above error message.

Scenario 2:

1. Logged in to Designer via SAP Authentication with user id USER2. Created a new test universe (Universe2) with option u2018Use single sign-on...u2019

Universe is working fine. Exported to repository.

2. Logged into InfoView via WindowsAD with user id USER2.

Created a test report (Report2) from the SSO universe. Report is working fine.

Saved the report in the public folder.

3. Logged into InfoView via WindowsAD with user id USER1.

Refreshed the saved report. But it is throwing error message u201CUnable to logon to BW logon data imcompleteu201D

Created a new report from the SSO Universe, but same above error message.

Note:

- I donu2019t have Xcelsius in my machine. BOE and Integration kit both are in same version (XI 3.1 sp3).

- We used IP address as Application server in CMCSAP and Universe Connection Parameter.

Sofa log detail is following:

Wed Jun 08 01:51:31.414 ThreadID<7180> SAPMODULE : Calling m_pRfcWrapper->RfcOpenEx() ...

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : RfcOpenEx(...) returned 0

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Unable to connect to SAP BW server connection closed without message (CM_NO_DATA_RECEIVED)Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Call to m_pRfcWrapper->RfcOpenEx() took 0.047 seconds

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Unable to authenticate using SNC because the URI does not meet the minimum connection requirements.

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Warning: SNC was enable and failed. The authentication process is falling back to secondary Credentials...

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Determining if we can connect using SSO. Calling CanAuthenticate...

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Authentication model for SAP connectivity is SSO

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : Serialized session exists, try deserializing it.

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : The SAP SSO authentication process will fail because the SAP secondary credential are not properly updated and the password is blank.

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : SAPSSOAuthenticationService::~SAPSSOAuthenticationService

Wed Jun 08 01:51:31.461 ThreadID<7180> SAPMODULE : SAPSNCAuthenticationService::~SAPSNCAuthenticationService

Why it is behaving like that?

Thanks for your help.

regards,

Kiruba v.r.

Former Member
Not what you were looking for? View more on this topic or Ask a question