Date: Tue, 30 Dec 1997 15:16:08 -0800
From: David.Brownell@Eng (David Brownell)
Message-Id: <199712302316.PAA28560@argon.eng.sun.com>
To: info@infochain.be, java-security@web2.javasoft.com
Subject: Re: user identifier
That's the intended role of a java.security.Principal -- and in fact,
the JavaServer product line uses it in exactly that way, supporting a
set of common authentication schemes in the same framework.
That support works with underlying OS authentication and X.509 public
key certificates (with SSL client authentication), of course. It also
works with the low security user database shipped with the web server,
and challenge/response authentication systems which (like most) rely
on a single challenge.
- Dave
> From info@infochain.be Tue Dec 30 11:17:38 1997
> Date: Tue, 30 Dec 1997 08:16:54 +0100
> From: "ir. Jan Honinckx" <info@infochain.be>
> To: java-security@web2.javasoft.com
> Subject: user identifier
>
> As we work with messaging software we are considering to write a
> cryptography extension to MQseries.
>
> A good product would have
>
> Certfication (possible through MessageChannelUserIdentifier)
> and encryption (many possible packages)
>
> Is it possible to have the link between JAVA Certification and the
> operating system security. In MQseries there is a very good Object
> Authority Manager, when we can link that to the incoming
> authentication, we can build a great product on the fly.
>
> Regards
>
>
> ir. Jan Honinckx
>
> MQseries certified engineer
> DB2 database administrator
>