Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
Has anyone found a way to successfully implement form-based login for Windchill 9.1? What I'm looking for is to eliminate the basic login popup and send the user to a simple login form instead, similar to how most other enterprise applications work.
One thing I'm worried about is that I don't know if Pro/E's integration with Windchill depends on basic authentication.
Thanks for any advice!
-Tom
Hi all,
a simple solution to this will be to implement a custom page in Apache for the "Login Authorization Failed" with all the info needed to solve login related issues.
Anyway, some time ago I implemented a form-based authentication system for Windchill in a development environment based in OpenSSO. It was a software developed by Sun Microsystems, and I wrote a custom login module, that was redirecting to form based authentication if the client was a browser (IE, Firefox, Chrome) and performing basic authentication in other cases. I tested it with web browsers, ProE, UG and Catia Worgrup Managers, and worked fine. However, other issues in the company where I was working with this, stopped the project, and never was implemented in a production system.
Another problem with OpenSSO is that Oracle bought Sun, and discontinued the OpenSSO project (perhaps to continue selling Oracle's SSO solution), but there is a fork of it called OpenAM that continues with the open source project.
Regards
Iker Mendiola
Prambanan IT Services
http://www.prambanan-it.com
Iker Mendiola - Prambanan IT Services |
[...] I wrote a custom login module, that was redirecting to form based authentication if the client was a browser (IE, Firefox, Chrome) and performing basic authentication in other cases [...]
I like that idea! We have a potential use for it as well - I'll try it out!
I've succeeded producing a Windchill integration to a SiteMinder-backed form-based authentication scheme used in a corporate intranet by transferring the user name into the servlet request from the SiteMinder HTTP header value (SM_USER) using a servlet filter. Turned out unfortunately that the Arbortext Editor component of the architecture won't support form-based authentication AT ALL - it only supports HTTP BASIC (not even DIGEST!) - so we had to scrap that idea and go with the common denominator of HTTP BASIC (it took quite a lot of explaining to corporate security why this enterprise tool had to pass credentials onto the wire in essentially cleartext!).
I would like for us to use form based for those user agents that will support it (such as everything but Arbortext Editor), however so - thanks for the tip!