[3496] in java-interest
Re: How java apps get krb tickets?
daemon@ATHENA.MIT.EDU (Mark Eichin)
Tue Nov 14 19:18:44 1995
From: Mark Eichin <eichin@cygnus.com>
Date: Tue, 14 Nov 1995 15:06:18 -0500
To: lsbart35@emmo.indy.cr.irs.gov
CC: acain@snapple.ncsa.uiuc.edu, java-kerberos@lists.Stanford.EDU,
www-kerberos@lists.Stanford.EDU, java-interest@java.sun.com
In-reply-to: <Pine.SUN.3.91.951114065338.13734B-100000@emmo.indy.cr.irs.gov>
(lsbart35@emmo.indy.cr.irs.gov)
> Yes, certainly the ease of use issue is important. Else, why would we
> bother adapting our applications to the Web? Else, why would we bother
> to use Kerberos to provide a "single login" access to multiple services?
If you have the java app prompt for a password and get it's own non
cached tickets, you've eliminated the entire single-signon aspect of
kerberos... unless, of course, you expect that users will *only* be
using kerberos through this java app; do you? Or are they just going
to have to give eudora their password again because the cache isn't
shared? (It also ignores forwarded credentials in V5, but presumably
the user is running the app locally anyhow...)
_Mark_
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
