Help

Icon - KMLM List KMLM List

View email archives for the history of this mailing list.

List Home All Archives Dates Threads Authors Subjects
sushidevelopers - Re: [sushidevelopers] new sushi deployment for testing Message Thread: Previous | Next
  • To: "Crego,Erin" <cregoe@xxxxxxxx>
  • From: Abdul Habra <ahabra@xxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 15 Jul 2010 09:42:17 -0400
  • Cc: "Boerema, Cate" <Cate.Boerema@xxxxxxxxxxxxxxxxxxxx>, <sushidevelopers@xxxxxxxxxxxxx>
Send Email to sushidevelopers@list.niso.org:
Send new message
Reply to this message

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?

Attachment: SUSHIauthentication20aug09.pdf
Description: Adobe PDF document


On Jul 15, 2010, at 9:17 AM, Crego,Erin wrote:

The username and password go as parameters on the URL.  So, it would look something like:
 
 
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Boerema, Cate
Sent: Wednesday, July 14, 2010 4:41 PM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] new sushi deployment for testing
 
Hi Erin,
 
Which SUSHI request elements do username and password map to (RequestorID, RequestorName etc)?
 
Thanks much,
 
Cate Boerema
 
 
 


By Date: Previous | Next Current Thread By Thread: Previous | Next