Difference between revisions of "Authorization Framework"

From Gcube Wiki
Jump to: navigation, search
Line 4: Line 4:
  
 
The service runs on a smartgears node.
 
The service runs on a smartgears node.
 +
 
It relies on a CouchDb instance to store the created tockens within a database named '''authorization'''.   
 
It relies on a CouchDb instance to store the created tockens within a database named '''authorization'''.   
In order to make the CouchDb visible to the service a RuntimeResource with Category '''Database''' and name '''AuthorizationDB''' must be created with an AccessPoint like the following:
+
 
 +
The service is expected to discover the CouchDb instance to use by relying on a RuntimeResource with Category '''Database''' and name '''AuthorizationDB'''. This resource must be created with an AccessPoint like the following:
  
 
<code>
 
<code>

Revision as of 16:36, 15 October 2015

The gCube Authorization service is a service that issues Authorization tokens in a gCube-based infrastructure.

Configuration Overview

The service runs on a smartgears node.

It relies on a CouchDb instance to store the created tockens within a database named authorization.

The service is expected to discover the CouchDb instance to use by relying on a RuntimeResource with Category Database and name AuthorizationDB. This resource must be created with an AccessPoint like the following:

     <AccessPoint>
           
        <Description>authorization acces point</Description>
           
        <Interface>
               
           <Endpoint EntryName="authorization">http://hostname:port/</Endpoint>
           
        </Interface>
           
        <AccessData>
               
           <Username>authz</Username>
               
           <Password>...</Password>
           
        </AccessData>
       
     </AccessPoint>