Hi,
Using Mit Kerberos how can I support SSO?
Is it possible to update Microsoft cache? How can I make other kerberised
application to use cache file which is generated by my application.
I mean when I got credentials (TGT) from KDC, I will store to cache file. I
will set it as default cache.
Eswar S wrote:
Hi,
Using Mit Kerberos how can I support SSO?
You can obtain your tickets during the windows logon process from your
domain controller and then access them from KFW aware applications by
setting the default ccache to MSLSA: or by permitting Network Identity
Manager to synchron
ive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
Message: 6
Date: Fri, 25 Jan 2008 18:52:32 -0500
From: Jeffrey Altman <[EMAIL PROTECTED]>
Subject: Re: support SSO in Windows with Keberos TGT
To: [EMAIL PROTECTED]
Cc: kerberos@mit.edu
Message
Eswar S wrote:
On Vista the MSLSA: cache is read-write provided you do not use the
binaries provided by MIT.
KFW 3.2.2 was built incorrectly and the MIT distribution treats the
Vista MSLSA: cache as read-only.
I want to update/add my credentials to Microsoft (windows XP & VISTA
&win2k
emination) by persons other than the intended recipient's) is
> prohibited. If you receive this e-mail in error, please notify the sender
> by
> phone or email immediately and delete it!
>
>
>
>
>
> Message: 6
> Date: Fri, 25 Jan 2008 18:52:32 -0500
> From: Jeff
Sylvain - MVP GPOs wrote:
Hi,
perharps you can have a look on www.centrify.com which provide a interop SSO
between Windows/Unix/linux based on Kerberos...
sylvain
How would that solve the "need a single credential cache" problem
that this thread is discussing?
smime.p7s
Description: S/M
sylvain cortes wrote:
it's managed by the centrify client deployed on the Unix/Linux host
You do understand that the issue here is how to use applications written
to use KFW
and applications written to use Kerberos SSP on the Windows platform
with the
same credential cache.
Are you suggesting
it's managed by the centrify client deployed on the Unix/Linux hostSylvain
CORTES [EMAIL PROTECTED]
> Date: Wed, 13 Feb 2008 18:46:17 -0500> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> CC: kerberos@mit.edu> Subject: Re: support SSO in Windows with
> Keberos
erberos@mit.edu> Subject: Re: support SSO in Windows with
> Keberos TGT> > sylvain cortes wrote:> > it's managed by the centrify client
> deployed on the Unix/Linux host> You do understand that the issue here is how
> to use applications written > to use KFW> a
sylvain cortes <[EMAIL PROTECTED]> wrote:
> So, for example, a windows computer which use Putty can present a
> kerberos ticket to a Unix machine with the Centrofy client, without
> any re-authentication. And Unix to Windows, or Unix to Unix works
> also in the same way.
You can do that without pa
CORTES [EMAIL PROTECTED]
> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> CC: kerberos@mit.edu>
> Subject: Re: support SSO in Windows with Keberos TGT> Date: Tue, 19 Feb 2008
> 13:08:22 -0600> > sylvain cortes <[EMAIL PROTECTED]> wrote:> > So, for
>
sylvain cortes wrote:
> hi - you always can do everything...it's a question about time ;-) I
> did the "classic" way before using centrify, and it was "hell" to
> maintain: manage the keytab, manage the "ad account", manage the NTP
> client to have the right ticket session, etc...
Sorry but NTP do
e.ntp newsgroup.
Danny
>
>
>
> > Date: Fri, 22 Feb 2008 18:14:24 -0500
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > CC: [EMAIL PROTECTED]; kerberos@mit.edu
> >
du> Subject: Re: support SSO
> in Windows with Keberos TGT> > sylvain cortes wrote:> > hi - you always can
> do everything...it's a question about time ;-) I> > did the "classic" way
> before using centrify, and it was "hell" to> > maintain
14 matches
Mail list logo
