Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



Eco Grid Auth Design

Difference between version 8 and version 3:

At line 10 added 3 lines.
+ The Metacat implementations of these new methods have been coded and are ready to be committed to the SEEK project. Placeholder 'implementations' have been added for SRB and Digir as well. These placeholders ignore the authentication credential parameter and call the existing service implementation methods that do not require authentication (query() and get()).
+
+
At line 19 added 1 line.
+ \\
At line 20 added 31 lines.
+ \\
+ \\
+ A snippet of what an embedded authenticationDomain would look like in a Registry entry is below:
+ {{{
+ <?xml version="1.0"?>
+ <reg:EcogridRegEntry
+ xmlns:reg="ecogrid://ecoinformatics.org/ecogrid-regentry-1.0.0beta1"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="ecogrid://ecoinformatics.org/ecogrid-regentry-1.0.0beta1 EcogridRegEntryType.xsd ">
+ <authenticationDomain>
+ <domainName>localhost</domainName>
+ <serviceOperation>serviceOperation</serviceOperation>
+ <serviceURL>http://localhost:8080/knb/services/EcoGridAuthLevelOneService</serviceURL>
+ <serviceClass>org.kepler.authentication.LDAPAuthenticationService</serviceClass>
+ </authenticationDomain>
+ <clusterName>localhost</clusterName>
+ <serviceName>Dora's Metacat EcoGrid QueryInterface</serviceName>
+ <wsdlURL>http://localhost:8080/knb/schema/EcoGridQueryInterfaceLevelOne/EcoGridQueryInterfaceLevelOne.wsdl</wsdlURL>
+ <serviceType>EcoGridQueryInterface</serviceType>
+ <endPoint>http://localhost:8080/knb/services/EcoGridQuery</endPoint>
+ <serviceClassification>Query Level One Class</serviceClassification>
+ <description>EcogridServiceRegistry</description>
+ <provider>dora</provider>
+ <documentType>
+ <namespace>eml://ecoinformatics.org/eml-2.0.1</namespace>
+ <label>Ecological Metadata Language 2.0.1</label>
+ </documentType>
+ </reg:EcogridRegEntry>
+ }}}
+
+ If the authenticationDomain element were omitted from registry service entries, and the registry listing included both an entry for the authentication service (with type {{<serviceType>EcoGridAuthInterface</serviceType>}}) where the clusterName tied this authentication service to an {{EcoGridQueryInterface}} type service we'd be close to solving the clustering problem. BUT...we would need a place to specify the authentication domain {{<serviceClass>org.kepler.authentication.LDAPAuthenticationService</serviceClass>}} element. Kepler uses this to present the user with the correct interface to login using the Ecogrid service.

Back to Eco Grid Auth Design, or to the Page History.