security-services message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: XPath Attribute Profile
- From: "Conor P. Cahill" <concahill@aol.com>
- To: SAML <security-services@lists.oasis-open.org>
- Date: Wed, 1 Jun 2005 11:38:05 -0400
So, why are we profiling this to be xpath based?
I would think a better solution would be along the lines of:
<saml:attribute name="urn:liberty:id-sis-pp:2003_08" ...
<saml:AttributeValue>
Normal PP Query results formatted data goes here
</saml:AttributeValue>
</saml:Attribute>
That way the IdP is able to just copy what it got back from PP (or what
it would have generated for its PP interface if it was the PP as well)
and it works generically for any service.
So, to clarify, I'm proposing that we:
- name the
attribute using the namespace (or, prerhaps the schema) for the service
- place
service document into the attribute value rather than making this look
like single valued attribute.
Conor
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]