Difference between revisions of "Authorization Framework"
From Gcube Wiki
(→Configuration Overview) |
(→Configuration Overview) |
||
| Line 10: | Line 10: | ||
<code> | <code> | ||
| − | <AccessPoint> | + | |
| + | <AccessPoint> | ||
<Description>Authorization access point</Description> | <Description>Authorization access point</Description> | ||
| Line 28: | Line 29: | ||
</AccessData> | </AccessData> | ||
| − | </AccessPoint> | + | </AccessPoint> |
| + | |||
</code> | </code> | ||
Revision as of 16:40, 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 access point</Description>
<Interface>
<Endpoint EntryName="authorization">http://hostname:port/</Endpoint>
</Interface>
<AccessData>
<Username>authz</Username>
<Password>...</Password>
</AccessData>
</AccessPoint>
