[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] XACML REST profile -- <content> vs <id>
Upon reading the draft text more closely in light of Craig’s question/comment, I think I see the disconnect. In the preface for section 2.4.2 Delete All Versions of a Policy, add: Assume a policy admin user instructs the client application to delete all versions of the policy having policy ID <12345>. <current steps to get entry point, get PAP list of policies> The app searches the ATOM list for an entry whose <ID> matches the policy ID <12345> of the policy to be deleted. The app issues a DELETE request for the content
URI of that matching entry. Danny Thorpe
Product Architect |
|
Quest Software -
Now including the people and products of BiTKOO |
www.quest.com From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org]
On Behalf Of Danny Thorpe I think how the XACML Policy Id value is mapped onto a REST URI corresponding to the policy document should be left up to the service implementer. When submitting a DELETE operation, clients should use the content URI. Clients should not be responsible for (and should be discouraged from) composing the
policy ID into a URI, since that mapping is determined by the service implementer and may vary from vendor to vendor. -Danny Danny Thorpe
Product Architect |
|
Quest Software -
Now including the people and products of BiTKOO |
www.quest.com From:
xacml@lists.oasis-open.org
[mailto:xacml@lists.oasis-open.org] On Behalf Of Craig R Forster Hi all, HTTP/1.0 200 OK
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]