[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] New Topic: Policy Provisioning
I think that there are a number of issues:
1) Very large feature set, a number of capabilities in the core set belong to web services development tools rather than provisioning, including schema and capability discovery. This places a burden on implementing SPML 2. This poses problems for vendors trying to implement SPML introducing the need to hand craft SPML implementations and for IT organizations in hand crafting client applications (requesting authorities) for those SPML providers rather than being able to generate code from WSDL.
2) Insufficient description of integration with security. There is no description of communication of the identity of the user submitting the request (identity of the RA), which may be necessary for authentication, authorization, and auditing. T
3) Insufficient feature set for enterprises wanting to develop simple self service user interfaces with web services.
WS-MEX/Transfer may be one approach. One of the key problems that it addresses is the need for out-of-band information that SPML does, which is related to the first point above.
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Hal Lockhart" <hlockhar@bea.com>
03/06/2007 09:50 AM |
|
Is SPML the proper protocol for policy lifecycle mechanisms? Seems like a bit of a stretch
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Prateek Mishra <prateek.mishra@oracle.com>
03/06/2007 08:56 AM |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]