Difference between revisions of "How To Configure gHN Security"
From Gcube Wiki
(New page: In order to enable gCube authentication and authorisation functionalities, gHN composing the infrastructure must be properly configured. The security configuration is needed to enable secu...) |
|||
| Line 1: | Line 1: | ||
| − | In order to enable gCube | + | In order to enable gCube security, gHN must be properly configured. As described in the [[GCube Security Model]], invocations to gCube Running Instances are protected using authentication and authorisation functionalities, provided by the [[Virtual Organisation Management]] subsystem. The security configuration of gHN is basically needed to enable authneticated invocations among gCube Running Instances, and to verify signatures of assertions about user's roles and membership. |
| − | The description of administrative steps | + | The description of administrative steps needed to enable security for gHN containers is available in the [https://wiki.gcore.research-infrastructures.eu/gCore-dev/index.php/Administrator_Guide#Configure_container_security Configure security] page of the gCore administrator's guide. |
Revision as of 12:36, 10 July 2009
In order to enable gCube security, gHN must be properly configured. As described in the GCube Security Model, invocations to gCube Running Instances are protected using authentication and authorisation functionalities, provided by the Virtual Organisation Management subsystem. The security configuration of gHN is basically needed to enable authneticated invocations among gCube Running Instances, and to verify signatures of assertions about user's roles and membership.
The description of administrative steps needed to enable security for gHN containers is available in the Configure security page of the gCore administrator's guide.
