OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: another attempt at azn query refinment

Before we try to work out whether or not this is a good solution, I propose
that we decide whether or not this a problem we are proposing to solve in
SAML 1.0. The kinds of questions you propose represent an entirely new kind
of question. "What is available for lunch?" is a very different question
from "May I have lunch?".

My gut reaction is that this is not something we should discuss in the SAML
1.0 timeframe.


-----Original Message-----
From: Simon Godik [mailto:sgodik@crosslogix.com]
Sent: Thursday, October 04, 2001 4:11 PM
To: 'security-services@lists.oasis-open.org'
Subject: another attempt at azn query refinment

I did not get response (negative or positive) to my previous message on azn
so here is another try.
Suppose we want to ask the question: What can I have for lunch today?
To rephrase: Can I have lunch today (yes/no) and if yes what is on the menu?
To answer, I propose to parameterize action element in authorization query:
<AuthorizationQuery resource="lunch">
                <ParamAction ActionName="eat">
                        <Parameter name="appetizer"/>
                        <Parameter name="main"/>
                        <Parameter name="desert"/>
        <Evidence> my weight is 500 lb</Evidence>
                <AuthorizationStatement resource="lunch" decision="Permit">
                                <ParamAction ActionName="eat">
                                        <Parameter name="appetizer">
                                        <Parameter name="main">

                                        <Parameter name="desert">
                        <Evidence> my weight is 500 lb</Evidence>

To support this schema modifications are minimal:
We can define ParamAction element and everywhere we allow Action now we can
choice of Action or ParamAction. We also need Parameter element which is
similar to
Attribute element. (Attribute element could be reused by I'm not in favor of
                <choice minOccurs="1" maxOccurs="unbounded">
                        <element ref="saml:Action"/>
                        <element ref="saml:ParamAction"/>
<element name="ParamAction" type="saml:ParamActionType"/>
<complexType name="ParamActionType">
                <element ref="saml:Parameter" minOccurs="0"
        <attribute name="ActionName" type="string" use="required"/>
<element name="Parameter" type="saml:ParameterType"/>
<complexType name="ParameterType">
        < same as AttributeType >
Simon Godik

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC