Currently a user must close all instances of a browser in order to logout of Windchill.
Please add a "logout" function to Windchill.
10.1 M010 and higher provide this feature if one configures Windchill to use form-based authentication (as this is the only reliable, cross-browser way to get logout).
There are downsides to form-based authentication from a user-perspective, of course -- primarily that in almost all cases one's authentication session will time out after being idle too long, e.g. if one goes out to lunch.
Why not use the same process that every other website on the internet uses for login/logout, including this community site? I can remain logged in all day on the community site and if I logout in one browser, I am logged out in all browsers. This seems like an issue that has been solved by everyone except the Windchill team.
When one uses basic authentication there is no reliable portable/cross-browser means of "logging out" -- the HTTP basic protocol simply does not provide for such functionality. The only reliable way of getting the browser to stop using the cached credentials is to close all browser windows.
Form-based authentication does have support for a logout. Form-based authentication and the logout feature first supported in 10.1 M010 can be used to logout of one's cookie-based authentication scheme across all browsers/windows.
Also to be clear, it is inaccurate to say that form-based authentication *always* has an obnoxiously short authentication timeout. It usually does -- particularly once security auditors get ahold of things, but this is not necessarily always the case. One can, however, configure a very long timeout.
Windchill 10.1 does not default to form-based authentication solution -- it defaults to HTTP basic authentication. It also does not select a form-based authentication solution for you -- that's up to you -- but it provides much better interoperability with form-based authentication than previous Windchill versions.
I don't know about protocols or form-based authentication, but when I log in and out of my bank's site from a browser, it seems to work pretty well and is very secure and I didn't have to configure anything.
What's the problem with making it work like that?
In short, the feature is in 10.1 M010 -- but is not the default configuration.
If you are on 10.1 M010 and select and configure a form-based authentication solution, then you can make it work like that.
If you don't then basic authentication is used as in previous releases and it can't and won't.
In another discussion a user posted a solution from GSO.
Actually, this doesn’t seem to work in Chrome. Instead, just add “username@” in front of the existing Windchill url and it will prompt you for the new credentials. (Don’t use the quotes and replace “username” with the actual user who you want to log on as.)
The reason Chrome hangs on to authentication is that when you close Chrome you will see several processes still running.
Just proved this out............................
Go to chrome://settings/search#continue%20running and deselect the button.
When you now close Chrome, all processes die and you are prompted for authentication again next time you access Windchill through Chrome.
That post that Marco shows will log you out of all sites you are logged into at the time. Logged in to 4 different sites. It logs you out of all 4 sites.
Or you can use the "New incognito windows" feature.
I saw that in Chrome until I found that there is a setting to not allow add-ons to run in the back ground when chrome is closed. now when I close chrome, no chrome process remain in the Task manager.
Log Off capability that is available with form-based authentication is not available with the default basic authentication and, therefore, is not described in detail in end user documentation
Refer following topics from Windchill Help Center:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.