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 - Gray areas: AuthN&AuthZ - Requestor ID/Customer ID Message Thread: Previous | Next
  • To: "sushidevelopers@xxxxxxxxxxxxx" <sushidevelopers@xxxxxxxxxxxxx>
  • From: Tom Demeranville <Thomas.Demeranville@xxxxxxxxxxxxxx>
  • Date: Thu, 20 Jan 2011 09:41:22 +0000
Send Email to sushidevelopers@list.niso.org:
Send new message
Reply to this message
Hello Sushi list,

I'm designing a SUSHI server at the moment and I've hit a couple of gray areas. 
  I'm hoping the list can help me out.


1)       Although the specification talks about security, it's rather vague and 
doesn't talk about interoperability, and I've also found contradictory 
recommendations in other documents.  For me, there are two main requirements, 
that it's secure and that it interoperates.  What should I be implementing to 
be compatible with existing clients?

2)      I'm confused about the role of Requestor ID vs Customer ID.  Some 
documentation states the Requestor ID is the client/service requesting the data 
and Customer ID identifies the customer.  Is this the case?   A quick glance at 
the list of current SUSHI servers shows that services are using these fields in 
many different ways.

Tom.

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