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; } } }

when creating new dcr login page popsup

cawabonga

Hello,
I have a problem with creating for e.g. new dcr's. When a user wants to create a new dcr he gets the login screen in the small window of the categorie/type chooser.
His browser accepts cookies and session cookies. The permissions of the user are also correct. I have no idea whats wrong.
Thanks in advance
Daan

Grtnz,
Daan

Find more posts tagged with

Comments

sajiddc

Do you see the similar behavior when you try to edit an existing DCR? How about previewing of files?

rajeshwarank

Does this happen often or only if a user logs in after say one or 2 days, because then try this out

Setting Login Authentication Expiration
If users log in to WebDesk, then close the window, then reopen WebDesk again within the
same user session on a machine within a 24-hour period, TeamSite recognizes them from their
previous login and does not require them to re-enter their username and password. This is
important for users of the Casual Contributor interface, who will be transferred directly to the
relevant part of WebDesk if they have previously logged in within the authentication period.
The default login authentication expiration is 24 hours. To change this value, edit the
ui_login_lifetime setting in the [authentication] section of iw.cfg using the
following syntax:
Configuring GUI Functionality
• ui_login_lifetime=ahbmcs (where a represents the number of hours, b represents
the number of minutes, and c represents the number of seconds)
• 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.
For example, to set the login authentication expiration to 2 days, enter 2D, as follows:
[authentication]
ui_login_lifetime=2D
To set the login authentication expiration to 8 hours, 15 minutes, and 7 seconds, enter
8h15m7s, as follows:
[authentication]
ui_login_lifetime=8h15m7s
To set the login authentication expiration to 1.5 years, enter 1Y6M, as follows:
[authentication]
ui_login_lifetime=1y6m
If you want the login authentication to never expire, enter infinite, as follows:
[authentication]
ui_login_lifetime=infinite
Similarly, the cookie_lifetime setting in the iw.cfg file controls the term for which browser
cookies are issued when users log in to WebDesk or WebDesk Pro. A value of 0 (zero) creates session
cookies, such that users are automatically logged out by exiting the browser. A value of infinite (which
is the default) causes persistent cookies to be issued, such that users stay logged in until the
ui_login_lifetime is reached or the user deliberately logs out. No other values should be used.

cawabonga

it also happens when previewing files etc.
Daan

Grtnz,
Daan

sajiddc

Most likely its a cookie/session timeout issue. Can you check your iw.cfg? If you need help please check your TS manual. It is explained there as to how you can change the session/cookie timeout. Also, make sure that you restart the TS services after that. See if that solves your problem or not.

Let me know how it goes

Adam Stoller

What version of TeamSite - on what platform?

As [at least] one of the responses pointed out - their could be an issue with the cookie/authentication lifetime specified within the iw.cfg file.

I believe (though don't recall 100%) that 5.0.1 (perhaps 5.5.1?) had a problem with one of these type settings such that if you used the word "infinite" it actually evaluated it to '0' and resulted in expiring the cookie directly after authenticating you - such that you could navigate all around the main browser window, but as soon as you tried to bring up a preview window (or edit a DCR in browser-mode) you would see the behavior you noted.

To the best of my knolwedge - this problem does *not* exist in 5.5.2 - hence my reason for asking what version of TeamSite you are using.

--fish
(Interwoven, Curriculum Development)

cawabonga

We are working with TS 5.0.2. and Windows 2000 server.

greetings Daan

Grtnz,
Daan

sajiddc

Daan,

Following up with your issue. Still experiencing the issue or has it been resolved?

cawabonga

one customer still has this problem.

Daan

Grtnz,
Daan

Adam Stoller

Could you perhaps post (or attach) a copy of your iw.cfg file? It might just help...

--fish
(Interwoven, Curriculum Development)

cawabonga

Hello,
Here is a copy of the iw.cfg file.

Daan

Grtnz,
Daan

Adam Stoller

Well, I don't see what I was explicitly looking for, but ... here are some comments and/or suggestions:

1) instead of 'ui_login_lifetime=24h' try 'ui_login_lifetime=1440'
2) you seem to have inconsistant host settings:
a) [iwcgi] > launchpad_hostname=spf-lgtwcm01
b) [teamsite_servlet_ui] > servlet_host=localhost
c) [iwwebd] > host=www.teamsite.lightning.philips.com
d) [iwproxy] > iwproxy_host=10.16.42.73
e) [iwproxy] > customer_webserver_host=10.16.42.73

On my, albeit standalone, laptop environment - I have a hostname for 'a' but I have an identical setting (localhost) for 'b' - 'e' - and I'm wondering if the one of those settings might be causing the problem. If you change them - I'm pretty sure you would need to do an 'iwreset -ui' to test them out.

I'm basically taking an "educated" guess here - so it is quite possible that this is a red-herring and has nothing to do with the problem you are experiencing - but hopefully it will help.

--fish
(Interwoven, Curriculum Development)