KMLM List
View email archives for the history of this mailing list.
|
|
|
|
sushidevelopers - RE: [sushidevelopers] new sushi deployment for testing
|
Message Thread:
Previous |
Next
|
- To: Abdul Habra <ahabra@xxxxxxxxxxxxxxxxxxxx>, "Crego,Erin" <cregoe@xxxxxxxx>
- From: "Andrew Wiles [aew]" <aew@xxxxxxxxxx>
- Date: Thu, 15 Jul 2010 15:16:10 +0100
- Cc: "Boerema, Cate" <Cate.Boerema@xxxxxxxxxxxxxxxxxxxx>, "sushidevelopers@xxxxxxxxxxxxx" <sushidevelopers@xxxxxxxxxxxxx>
- Send Email to sushidevelopers@list.niso.org:
- Send new message
- Reply to this message
|
Another method we've seen used for authentication are the WSS extensions to
SOAP requests. ProQuest and Swetswise use this method.
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
Behalf Of Abdul Habra
Sent: 15 July 2010 14:42
To: Crego,Erin
Cc: Boerema, Cate; sushidevelopers@xxxxxxxxxxxxx
Subject: Re: [sushidevelopers] new sushi deployment for testing
I found this attached pdf on niso site.
http://www.niso.org/apps/group_public/download.php/2650/SUSHIauthentication20aug09.pdf
If I understand it correctly, It states that the user name/password could be
embedded in the RequestorID
Additionally, SOAP allows the envelope to be posted with an http GET (and POST
of course)
So if the client uses GET, adding username/password as parameters to the URL,
would it not break the soap request?
|
|
