nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 7.2.1 login/cookie lifetime ?

nipper

Linux, TS 7.2.1.

I changed application.xml for the cookie to be infinite (and since it says it expires in 2074 I think that works).

I also have the following in the correct iw.cfg (/etc/iw.cfg verified with iwlocation):

[authentication]
authenticate_by=file local
cookie_lifetime=5D
ui_login_lifetime=5D

I am still getting dropped out multiple times a day. Login, kill IE, and go to http://server/iw-cc/command/iw.ccpro.filesys it requires me to login again.

Cannot find anything talking about this changing in the manuals.

Any ideas ? Anyone else on 7.2.1 see the same thing ?

Andy

Also tried:

[authentication]
ui_login_lifetime=96h00m00s

Per the latest KB I could see, same results.

Find more posts tagged with

Comments

mart2001

I am seeing that the TeamSite 7.2.1 is dropping me out a lot sooner than the TeamSite 6.7.2, although I have not tried changing the configs to make them last longer.

nipper

Yea I have tried it on 2 Linux installs, both drop you quick. I opened a case. I will get back in a couple months when someone responds. Smiley Very Happy

Adam Stoller

FWIW - from a recent Support Case of mine:

[2010-12-17] Is there something intrinsic in 7.2.0 (as compared to say 6.7.2) that causes the user's authentication cookies to disappear / become invalidated as soon as the browser window is closed (*not* having clicked on the logout link)?
In 6.7.2 - I login, and then close my browser window, open a new one, go to the TS url and continue from where I left off without having to login again until [by default] 24 hours have elapsed since my last login (-or- I explicitly logout).
In 7.2.0 - I login, and then close my browser window, open a new one, go to the TS url and have to login again regardless of how recently I logged in before (i.e. 2 minutes ago)
This is *not* a browser setting (I'm using the same browser on the same desktop machine to connect to both a 6.7.2 and 7.2.0 server).
This is *not* an iw.cfg setting or IWHOME/local/config/lib/content_center/customer_src/etc/conf/customer/*.xml setting -- at least not with respect to anything explicitly saying that the cookie should be invalidated on-close of the browser window.
Is this due to the switch to Jboss?
Is there a way to configure jboss or TS to once again provide a 24-hour (+/- as desired) authentication cookie as long as the user does not explicitly logout of TeamSite?

[2010-12-20] I was able to reproduce the issue as you described. This might be related to jboss. I will do some more research and get engineering's help if needed.
I will keep you posted about the progress.

[2010-12-21] I have done some research and found out this is a known issue which has been introduced as a side effect of implementing a new feature in TS7.x. The new feature is if a user not hitting the server for certain time period, the user session automatically timeout. This feature is likely to introduce the above side effect.
Is this a big issue for your company? It seems to make the application more secure.
Anyway, we already have an issue filed in the internal system and engineering will look into this in the future release. As for now, there is no workaround.

[2010-12-21] If there is a BUG or Feature Request ID associated with this item - please provide it so that I can provide that information to my customer - and let them decide what they want to do about it.
I might do so for myself personally after the new year as I'm hoping to install 7.2.1 on my dev machine over the holidays - we'll see.

[2010-12-22] FYI, here is the product issue ID: TS-13251. You can use the ID for a reference when talking to our support.

As far as I know, my customer hasn't pursued this any further and neither have I (yet). Hope that helps.

nipper

Well I know this is an issue at 2 of the 3 companies I have upgraded to 7.2. Thanks for the bug ID. Hope this gets some viability.

Andy

Adam Stoller

Well I know this is an issue at 2 of the 3 companies I have upgraded to 7.2. Thanks for the bug ID. Hope this gets some viability.

Andy

And maybe some visibility too ;-)

Gregg Faus

Anyone have an idea what a fix for this will be released? Autonomy hasn't updated TeamSite since October of last year. Makes me wonder why we pay maintenance any more.

nipper

Anyone have an idea what a fix for this will be released? Autonomy hasn't updated TeamSite since October of last year. Makes me wonder why we pay maintenance any more.

Never heard anything. I would suggest talking to you sales critter, but there has been a lot of turnover in that so you likely do not know who it is.

Gregg Faus

but there has been a lot of turnover in that so you likely do not know who it is.

You're exactly right. I think we have a new rep every year. The last time I met with a rep all she did was push new products on us. And when my answer was no, her reply was "can I speak with another person in your organization who might need it. Can I have their name and number?". Ugh.

nipper

Well then you are only 1 behind. The new one is out of CA (since we are covered by the same rep).

Migrateduser

We just upgraded to 7.2.1 on Linux and are seeing the same issue with TS killing users sessions while they're in the middle of normal operations. This is a huge step backward.

I have tried to find where this is even documented:

[authentication]
ui_login_lifetime=5D

Which doc explains this attribute?

ISCBorisB

We just upgraded to 7.2.1 on Linux and are seeing the same issue with TS killing users sessions while they're in the middle of normal operations. This is a huge step backward.

I have tried to find where this is even documented:

[authentication]
ui_login_lifetime=5D

Which doc explains this attribute?

Older Documentation versions (Up to 6.1 or 6.5 perhaps) had it documented in Administration Guide,
under "Setting Login Authentication and Cookie Expiration". Then the paragraph simply disappeared.
Here is an excerpt. Please note that I do not know if the following is still valid in TS 7.X

- ui_login_lifetime=ahbmcs (where a represents the number of hours, b represents
the number of minutes, and c represents the number of seconds) OR
- ui_login_lifetime=xYyMzD (where x represents the number of years, y represents
the number of months, and z represents the number of days)
When specifying years, months, or days, Y, M, or D must be upper-case.

Few Samples:
ui_login_lifetime=2D # Two Days
ui_login_lifetime=1Y6M # 1.5 years
ui_login_lifetime=8h15m7s # 8 hours, 15 minutes, and 7 seconds

Migrateduser

Thanks Boris. So apparently we can no longer control a user's login session? This is already an issue and we've only been up in 7.2.1 for 3 days. I know I set something up in 6.7.2 so that users timed out in 24 hours or something like that. Or when they close their browser they have to login again when they open a new one. I just can't recall where I set that up.

Anyone have any news on a resolution for users sessions just crapping out in the middle of normal operations?

nipper

Nope, esp on Linux.

If you rebuild the GUI (common with LiveSite), often kill the browser it fails.

Now one trick I have noticed is that if you get the login as part of a frame or as a popup, you can hit F5 and send the data and the login is back. Wonderful security feature.

Migrateduser

If you rebuild the GUI (common with LiveSite), often kill the browser it fails.

Can you retype this in English, please? Smiley Very Happy

nipper

Can you retype this in English, please?

smarta$$

If you rebuild the GUI, that drops your session. Often killing the browser does as well. Now do you want me to translate that to Texan for you ?

Migrateduser

No, y'all typed that one betterer. Smiley Tongue

We have noticed that users are thinking TeamSite is down because they lost their session. They have to close their browser window and open a new browser window to be able to continue what they were doing. Is this what you've seen as well?

ISCBorisB

Thanks Boris. So apparently we can no longer control a user's login session? This is already an issue and we've only been up in 7.2.1 for 3 days. I know I set something up in 6.7.2 so that users timed out in 24 hours or something like that. Or when they close their browser they have to login again when they open a new one. I just can't recall where I set that up.

Anyone have any news on a resolution for users sessions just crapping out in the middle of normal operations?

Dave - in case you still need this.
I came across the following looking for something else and remembered this thread...

Check User Interface Customization Guide, Customizing Content Center Application,
Paragraph "Configuring ContentCenter Authentication Cookie Expiration"

Migrateduser

Thanks Boris - I'll check that out (was OOO for the last week - was not ignoring you - and you know I would never miss an opportunity to increase my post count) Smiley Happy

UPDATE: OK that looks familiar from 6.x. We currently have the cookie lifetime set to "0", which from the doc implies that users should be logged out when they close their browsers. This is how we set things up in our 6.x environment as well. Does this mean whatever internal session timeout value is set will be ignored? The doc isn't crystal clear on that (surprise!).

ISCBorisB

Thanks Boris - I'll check that out (was OOO for the last week - was not ignoring you - and you know I would never miss an opportunity to increase my post count)

You definitely have your digital rights to ignore any post or anybody!

Jenni

Hi Dave,

Can you be specific on which file you changes for increasing the lifetime of the user session? We are having the same issue.

Migrateduser

Hi Dave,

Can you be specific on which file you changes for increasing the lifetime of the user session? We are having the same issue.

I'm not certain this all works properly, but this is the section Boris referred to in the UI Customization doc:

When a user logs into a ContentCenter GUI, a browser “cookie” is generated containing some authentication information, including a value for how long the browser should store this cookie. By default, the lifetime of these cookies is set to be infinite, resulting in persistent session cookies being issued and users remaining logged into TeamSite until either their TeamSite timeout value expires or the user deliberately logs out.
To configure the ContentCenter GUIs to issue non-persistent session cookies, so that users will be automatically logged out from TeamSite whenever they close their browsers, edit application_custom.xml:

[HTML]

[/HTML]

No values besides 0 and infinite can be specified. This behavior must be specified at the applications level.

Jenni

I'm not certain this all works properly, but this is the section Boris referred to in the UI Customization doc:

Thanks Dave. We already tried that option and did not work for us.

TS 7.2.1
Win 2008