BO XI thrusted SSO error

[mccom]

Hi,

we have a problem with our sso configuration.
We have BO XI installed on two suse linux servers as cluster and use a WebSphere Application Server Cluster on two windows maschines as webserver. The servers are all configured with dns and they can reach each other (no firewalls between). We use a non-root user to run the cms on linux and a different user under which the websphere servers are running on win2003.
Our report-users will be authenticated during a portal-login (WPS) and were redirected to InfoView when needed.
We have configured the thrusted sso as described in the bo documentation (sso enabled, SharedSecret, get the user from REMOTE_USER, etc.) but it is not working.
We get an in my eyes incompleted error-message in our websphere logs:

"Verbindung zu Dienst vom Server über CMS konnte nicht hergestellt werden"

translated:

"Can not connect to service from server via CMS"

I haven't removed anything like servername or cmsname from this message. It's the original one.

We get the normal infoview-loginscreen where I'm able to login.

We have a development environment (not clustered and all servers are windows maschines) where the hole thing works fine.
We are not sure if this is a linux problem or a cluster problem or both. I could imagine that the secEnterprise.dll is not able to connect to the cms server on the linux maschine during sso time, but why can I login when I fill out the infoview login form ?

Any help would be great.

 

[mccom]

Forgotton to say that we use BO XI Enterprise R2 SP2.

 

[mccom]

Hi,

we found out that this seems to be a cluster-problem.
We configured our web.xml like this:
...
<context-param>
<param-name>cms.default</param-name>
<param-value>@CMSSERVER1</param-value>
</context-param>
..
...
..
<context-param>
<param-name>cms.clusters</param-name>
<param-value>@CMSSERVER1</param-value>
</context-param>
<context-param>
<param-name>cms.clusters.CMSSERVER1</param-name>
<param-value>cmsserver1:6400,cmsserver2:6400</param-value>
</context-param>
...

When we change the cms.default param to point directly to one of our cms-servers the sso is operational.
Do anyone has successfully configured a trusted sso with a cms-cluster ?