BOE 3.1 SSO InfoView versus OpenDocument

[Former Member]

First off - InfoView Single Sign On works fine.

OpenDocument SSO (URL link in an email sent by BOE) does not work. Always prompts for windows login. If I provide the parameters the report runs fine. But obviously not acceptable by my users.

Note we are not using SiteMinder.

In my Web.config file for InfoView, the value for trusted.auth.user.retrieval is blank as well as trusted.auth.user.param. So I left them blank in the Web.Config file for InfoView. Is this the problem? Which setting should I use?

I did find a ticket in SAP (1255277) where it says SSO OpenDocument was fixed in a Fix Patch 1.

If that is the case, I have installed some patches to 3.1, but it has been awhile and I am not sure what patch level I am at.

How would I determine what patch level I am at to see if I am up to date?

[former_member192142 · Accepted solution]

Hi,

You probably do, but are you using the fully qualified path for your opendocument function, e.g.: <server>.bo.com and not just <server>

-J

[Former Member]

I did find out how to determine what version and service pack you are running from the SAP tech.

Go to either CMC or InfoView About screens. Look for the Product number.

For example: Product 12.1

I was told by the SAP rep yesterday that the 12 equates to version BOE 3.1

And the .1 part equates to Service Pack 1 has been installed.

If it were a .2 then Service Pack 2 would have been installed.

I found it a bit amusing when the SAP Tech said everyone always asks how to determine what version and service pack or fix patch that they have running. Maybe that should be SAP's first clue that they more info in their About screen.

[BasicTek]

How about program files > Business Objects 3.1 > Business Objects Enterprise > Software Inventory Tool. That's all i use. Takes a minute to load.

Regards,

Tim

[BasicTek]

ok you mention web.config which infers .net is being used. The bug was for java (web.xml). I'm not sure there is a bug for .net for this. In java it was fixed in fixpack 1 for 3.1 and service pack 2. If not using trusted authentication then this shouldn't be a concern.

Regards,

Tim

[Former Member]

That is correct I am using .net version of tools.

I put in a incident with SAP. Worked with them for about 2 hours yesterday. We compared InfoView config file to the OpenDocument config file. SSO in InfoView works all the time.

Tech had me change a couple settings in the config file. Restarted IIS and URL reporting still does not work. Another Tech is supposed to contact me back today. I don't feel so bad now that SAP cannot get it to work either. I will post the resolution if I ever find one.