back button does not work, posted by Guenter Nowak on Mon Dec 6 17:42:59 2004
|
hi
the back button/liunk does not work
if i click on an entry and then back, it does not work properly, i see the
|
Re: external authentication possible?, posted by Stefan Ritt on Mon Dec 6 21:22:20 2004
|
> In order to avoid having to remember multiple usernames/passwords for
> different systems, is it possible for ELOG to use external authentication
> via Active Directory, etc?
|
|
Re: back button does not work, posted by Stefan Ritt on Mon Dec 6 21:48:19 2004
|
> hi
> the back button/liunk does not work
> if i click on an entry and then back, it does not work properly, i see the
|
|
Re: external authentication possible?, posted by Steve Jones on Mon Dec 6 22:48:19 2004
|
> > In order to avoid having to remember multiple usernames/passwords for
> > different systems, is it possible for ELOG to use external authentication
> > via Active Directory, etc?
|
Re: external authentication possible?, posted by Steve Allen on Tue Dec 7 01:18:14 2004
|
> > > In order to avoid having to remember multiple usernames/passwords for
> > > different systems, is it possible for ELOG to use external authentication
> > > via Active Directory, etc?
|
|
Re: back button does not work, posted by Guenter Nowak on Thu Dec 9 11:30:49 2004
|
> > hi
> > the back button/liunk does not work
> > if i click on an entry and then back, it does not work properly, i see the
|
|
Re: external authentication possible?, posted by Stefan Ritt on Sun Dec 12 12:49:06 2004
|
> The only common denominator that could possibly cover all contingencies would
> be LDAP authentication. One way of doing this in a more-or-less universal
> fashion is to offload the auth task from eLog itself and place the burden on
|
Re: external authentication possible?, posted by Steve Jones on Wed Dec 15 15:42:13 2004
|
> > The only common denominator that could possibly cover all contingencies would
> > be LDAP authentication. One way of doing this in a more-or-less universal
> > fashion is to offload the auth task from eLog itself and place the burden on
|