The APIs have changed between 4.0 and 4.2, and the PIPs and PDPs need
to be rewritten. The most suitable document is http://www.globustoolkit.org/toolkit/docs/4.2/4.2.0/security/wsaajava/mig/index.html#wsaajava-migrating-GT4.0
, which describes migrating from 4.0 to 4.2, and that should highlight
all the interfaec changes.
Rachana
On May 24, 2010, at 5:17 AM, kanchanna wrote:
Hi All,
We have successfully tested the 'XACML Authorization Callout' PDP
with Globus 4.2
Our next step is to get the 'XACML Callout' PDP working with Globus
4.0, since our middleware is based on globus 4.0.
From the documentation, we learn that the Authorization Framework
has been changed since Globus 4.2.
In our experiment we have used the 'AuthzProfile' PIP with 'XACML
PDP' to push attributes as described in OSG/EGEE Authorization
Interoperability Profile <http://www.fnal.gov/docs/products/voprivilege/focus/AuthZInterop/documents/AuthZInterop%20XACML%20Profile%20v1.0.pdf
> (since our authorization service is based on the OSG/EGEE interop
profile).
The 'AuthzProfile' PIP is available only for Globus 4.2. We would be
grateful if the globus experts could give us directions on porting
the AuthzProfile PIP & XACML PDP to work with Globus 4.0(if it is
feasible at all, changes that would be required on globus 4.0 authz
framework, or replacing the Authz handler with that of 4.2(would
that help?), any compatibility issues etc.,). Which would be the
best way to approach for a solution on this?
Thanks in advance.
Regards,
Kanchanna
Rachana Ananthakrishnan
Argonne National Lab | University of Chicago
