Difference between revisions of "How To Configure gHN Security"
From Gcube Wiki
| Line 1: | Line 1: | ||
| − | In order to enable gCube security, | + | In order to enable gCube security, gHNs must be properly configured. As described in the [[GCube Security Model]], in a secure infrastructure invocations to gCube Running Instances are authenticated and authorised. The security configuration of gHNs basically enables authentication and authorisation functionalities that are used when a request is received by a Running Instance deployed in a gHN. |
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 container security] section of the gCore administrator's guide. | 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 container security] section of the gCore administrator's guide. | ||
Latest revision as of 12:58, 10 July 2009
In order to enable gCube security, gHNs must be properly configured. As described in the GCube Security Model, in a secure infrastructure invocations to gCube Running Instances are authenticated and authorised. The security configuration of gHNs basically enables authentication and authorisation functionalities that are used when a request is received by a Running Instance deployed in a gHN.
The description of administrative steps needed to enable security for gHN containers is available in the Configure container security section of the gCore administrator's guide.
