Single AD Sign-On

[Former Member]

Single sign on works fine the first time someone goes in, but if they leave their session unattended, and the timeout runs out, it says session expires and makes them log in. What is the point of single sign on then. Is this the way it is supposed to work. Shouldn't it just re-log them in using single sign on again if there is an available session.

My users are probably going to kill me over this. Please help.

[former_member136842 · Accepted solution]

Hi Karen,

which Version of BO ? Rel.2 or XI3.x ?

There is a default Timeout for the InfoView Application in the web.xml file on your Tomcat. Default is 20 Minutes. Maybe they get logged of after those 20 Minutes ?!

Regards

-Seb.

[Former Member · Accepted solution]

Yes, I know about the timeout setting. That's what I'm asking though. After the timeout has expired, if there is a session available, why can't the user just be "logged back in" without having to manually type a user-id and password. I mean, isn't that was single sign on is about.

[Former Member · Accepted solution]

In the Web.xml file look for the following entry

<param-name>logontoken.enabled</param-name>

<param-value>true</param-value>

and make sure that the value is set to "true".

[Former Member · Accepted solution]

Thank you very much. This does seem to work. However, I noticed that resulted in a new problem. I logged in as a test user and verified that I could see that user in the CMS server. Our timeouts are set to 10 minutes. According to the CMS server, it dumped that user earlier then 10 minutes (which is another problem). After 15 minutes, I was able to run another report without being prompted for a login. However, now my test user is now tying up 2 licenses.

[BasicTek · Accepted solution]

>

> Thank you very much.  This does seem to work.  However, I noticed that resulted in a new problem.  I logged in as a test user and verified that I could see that user in the CMS server.  Our timeouts are set to 10 minutes.  According to the CMS server, it dumped that user earlier then 10 minutes (which is another problem).    After 15 minutes, I was able to run another report without being prompted for a login.  However, now my test user is now tying up 2 licenses.

are you using the session cleanup listener on XI 3.x? if so comment that out in the web.xml

-Tim

[BasicTek]

Shouldn't it just re-log them in using single sign on again if there is an available session

The logontoken from the last post should correct this(it is also normally enabled by default). If not what type of SSO? web/app?

Saving the logon URL(ends in logon.do, logon.aspx, or logon.jsp depending on web/app and version) will allow anyone to re-init the SSO process by selecting the link from their favorites (that should help).

Regards,

Tim