Re: Re: Re: Re: MySQL, PERL and web authentication

My organization is in the process of implementing single sign-on for web based applications using an authentication server with cookies. We haven't yet run into these problems.

Are your certificates issued by a well know CA, such as Verisign? Which versions of Netscape encounter the redirect warning?

Comment on Re: Re: Re: Re: MySQL, PERL and web authentication

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: MySQL, PERL and web authentication by wardk (Deacon) on Jan 10, 2001 at 23:11 UTC
We do use cookies post-login with a single authentication application. The login app is something other apps just "plug-in", due to it's design (I wasn't there then, and am just getting my feet wet with it now) it authenticates then redirects to the appropriate system they were logging into (many of which are not https). This SSL hosted redirect causes netscape to put up a dialog, but has no "check here to not ask again" so the user can avoid getting it next login. On the certificate, the users are only being asked once a year (or if their machines are re-genned, new computer, etc). Aparently that is just too often...go figure.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: MySQL, PERL and web authentication
by wardk (Deacon) on Jan 10, 2001 at 23:11 UTC

We do use cookies post-login with a single authentication application. The login app is something other apps just "plug-in", due to it's design (I wasn't there then, and am just getting my feet wet with it now) it authenticates then redirects to the appropriate system they were logging into (many of which are not https).

This SSL hosted redirect causes netscape to put up a dialog, but has no "check here to not ask again" so the user can avoid getting it next login.

On the certificate, the users are only being asked once a year (or if their machines are re-genned, new computer, etc). Aparently that is just too often...go figure.

[reply]