|
From: Ronald v. K. <rv...@ab...> - 2003-04-07 10:40:40
|
I agree with this order, and with session info as well. SAML based authentication would be possible then as well. Embedded webserver is nice in some instances, but since tomcat is not that heavy, embedding tomcat (see the site how to do that) is an option, but just running it inside tomcat and making use of all the features it has regarding certificates etc. sound better to me. But he... that's just me Ronald Mayne, Peter probeerde het volgende duidelijk te maken op 07-04-03 07:15: > I'd modify "client authentication remote user passing" to "session > information passing". Including all session information (HTTP headers, > time of connection, etc as well as remote user/host/address, and the > equivalent for SMTP) allows for uses in the future that we don't think > of right now. > > If we're adding the user as metadata, it can't be too hard to add > everything else as well (can it?). > > My personal priority order would be > > 1 session information passing > 2 AXIS (no more Sun bugs) > 3 client certificate authentication > 4 embedded web server > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > > -----Original Message----- > *From:* Patrick Yee [mailto:kc...@ce...] > *Sent:* Monday, 7 April 2003 2:52 PM > *To:* ebx...@so... > *Subject:* [ebxmlms-develop] hermes 1.0 > > Now, Hermes development is turning to version pre-1.0. We are > refining the internal package structure and after that we want to > invite you guys to join the development. I think this is valuable > for Hermes development as we don't have time and resources to > address all requirement in Hermes 1.0. Now, at least we have the > following pending items: > > . client certificate authentication > . client authentication remote user passing > . AXIS > . embed web server > > What do you think? > > Regards, -Patrick > > >The information contained in this email and any attachments to it: > >(a) may be confidential and if you are not the intended recipient, any interference with, >use, disclosure or copying of this material is unauthorised and prohibited; and > >(b) may contain personal information of the recipient and/or the sender as defined >under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to >collect, hold and use such information and any personal information contained in a >response to this email, for any reasonable purpose in the ordinary course of >Spherion's >business, including forwarding this email internally or disclosing it to a third party. All >personal information collected by Spherion will be handled in accordance with >Spherion's Privacy Policy. If you have received this email in error, please notify the >sender and delete it. > >(c) you agree not to employ or arrange employment for any candidate(s) supplied in >this email and any attachments without first entering into a contractual agreement with >Spherion. You further agree not to divulge any information contained in this document >to any person(s) or entities without the express permission of Spherion. > > > > |