RE: Schema change requested

[Tim Moses <tim.moses@entrust.com>]

Title: RE: Schema change requested

Phill - Perhaps.  I prefer to think of it like this ...

Must have at least one way of referring to the subject, either by name, by artifact or by assertion ID.
And may have any number of queries (authentication or attribute).

I don't think that is what you said, is it?

All the best.  Tim.

-----------------------------------------
Tim Moses
Tel: 613.270.3183

-----Original Message-----
From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
Sent: Monday, October 08, 2001 3:54 PM
To: 'Tim Moses'; Hallam-Baker, Phillip
Cc: 'Oasis security services bindings'
Subject: RE: Schema change requested

I think what you want is more like the following:

        <complexType name="RequestType">
                <complexContent>
                        <extension base="samlp:RequestAbstractType">
                                <sequence>
                                        <choice>
                                                <element ref="samlp:Query"/>
                                                <element
ref="samlp:SubjectQuery"/>
                                                <element
ref="samlp:AuthenticationQuery"/>
                                                <element
ref="samlp:AttributeQuery"/>
                                                <element
ref="samlp:AuthorizationQuery"/>
                                                <element
ref="saml:AssertionIDReference"/>
                                                <element
ref="samlp:AssertionArtifact"/>
                                        </choice>
                                        <choice minOccurs="0"
maxOccurs="unbounded">
                                                <element
ref="saml:AssertionIDReference"/>
                                                <element
ref="samlp:AssertionArtifact"/>
                                        </choice>
                                </sequence>
                        </extension>
                </complexContent>
        </complexType>

In other words must have at least one request element followed by as many
Assertion ID requests as you like.

                Phill

Phillip Hallam-Baker FBCS C.Eng.
Principal Scientist
VeriSign Inc.
pbaker@verisign.com
781 245 6996 x227

-----Original Message-----
From: Tim Moses [mailto:tim.moses@entrust.com]
Sent: Monday, October 08, 2001 3:28 PM
To: 'pbaker@verisign.com'
Cc: 'Oasis security services bindings'
Subject: Schema change requested

Phill - It is the consensus of the Bindings group that the protocol schema
should be modified as described in the referenced message, in order to allow
a relying party to include an artifact in a SAML request for specific
attributes.
http://lists.oasis-open.org/archives/security-bindings/200109/msg00018.html
Could you please make the necessary adjustments so that the focus group may
consider the question.  Thanks very much.  All the best.  Tim.
-----------------------------------------
Tim Moses
Tel: 613.270.3183

-----------------------------------------
Tim Moses
Tel: 613.270.3183