xspa-interop-tech — archive

[Jiandong Guo]

  
  


Yes, we'd also like to demo how to manage and validate the SAML
assertion on the services side with

the service side STS and the service itself. It will be interesting
that we can interact with the existing components

for authorization (XACML) and attributes (HL7, etc).


One thing we can do is to profile

the Claims element with a specific Dialect
(http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html#_Toc162064957)

for XSPA use.


This can be used by the service provider to specify the specific
attributes it requests and by the client to pass the request to the STS

and even a way to inject the attributes values if handled properly.


Thanks!


Jiandong



Staggs, David (SAIC) wrote:
3257973E30B1E84DA4481E6C22B5F1D302A7FE46@VANCRMSGW1.vha.med.va.gov" type="cite">
  
  
  
  
  
  
  

  

  

  
I agree a vendor-provided
WS-Trust interactions on the
Service Provider side in which the received SAML assertion is validated
and
potentially authorized would be appropriate.  Jiandong,
is that your intention, too?
  

3257973E30B1E84DA4481E6C22B5F1D302A7FE46@VANCRMSGW1.vha.med.va.gov" type="cite">
  

  

  

  
I’ll be on travel next
Tuesday at HL7.  Since I am leading a TC there
all
Tuesday I will not be able to join the call.  Please
elect a new scribe for your
meeting so I can read your minutes. 
  I look forward to reading about the possible WS-Trust options
we can
demonstrate.  
  

  
Best regards,
  
David
  
David Staggs, JD, CISSP
(SAIC)
  
Veterans Health
Administration
  
Chief Health Informatics
Office
  
Standards and
Interoperability
  
Office: 858 433 1473