Personal tools
You are here: Home GRIA Documentation Documentation 5.2 Reference Manuals OGSA-DAI User Guide Developers' Guide Client Developer Using the OGSA-DAI API Integration with the GRIA Membership Service

6.1.2.3. Integration with the GRIA Membership Service

Up one level
The OgsaDaiSAMLHandler gets SAML tokens from a GRIA Membership Service and includes them with OGSA-DAI client methods.

Introduction

If access to a data resource subscription is controlled by a membership group (i.e. a SAML token is required to use it) then the token must be included in the OGSA-DAI API calls made to the service. This is done through one of the Axis handlers.

Configuration

Just like in the normal graphical GRIA client, a client.state file is used to configure which membership group to use. The client.state file contains information to say which the "default membership group" is. The easiest way to create a suitable client.state file is to copy one from the graphical GRIA client.

Run the GRIA Client as normal, drag the WSDL link from your membership service in to the client. Right click on the group you want to make your default and select "Set as default group"

Client selecting default membership group

Client selecting default membership group

Copy the client.state file from the gria client's configuration directory into the classpath of your application.

It is recommended that before doing this you make a back-up of the graphical client's client.state file and delete it from the client's configuration directory. This will make a fresh client.state file when you do the above process.