The security components (GSA, GSM, GSC and Processing Unit) can each have their own security configuration. As such, you can have different security behaviors even between Processing Units. But, all have one common concept: all configurations are declared using properties (either located in a properties file or part of the components properties).
The security implementation dictates the properties needed for configuration. For example, if you consider the out-of-the-box file-based security implementation, you can either rely on the defaults or configure the file location, password encoders, etc.
When a secured component is started, it looks for the security configuration properties in order to instantiate the security implementation.
Any configurations that are applied can be seen by setting the logging level to CONFIG (see
com.gigaspaces.security.level = CONFIG
The security properties file is used to configure the
SecurityManager, that is responsible for the authentication and authorization process.
security.properties file is common to all components and is usually located under
To only affect the Web Management Console, use the
The configuration file can be located anywhere in the classpath or in the classpath under
Alternatively, a system property can be set to indicate the location of the properties file:
-Dcom.gs.security.properties-file = my-security.properties
-Dcom.gs.security.properties-file the property file will be located as a direct path (e.g.
a resource (e.g. "my-security.properties") in the classpath or in the classpath under
Since System Properties are JVM level, any Processing Unit deployed within a GSC will also benefit from this configuration.
But, if security configurations were provided as part of the
pu.properties they will be used instead.
For a standalone Space, the default Space security configuration file is
Just like the
pu.properties, you can include the security properties as part of the custom properties being passed to the space
The default Processing Unit (Space) security configuration file is
This is equivalent to custom properties being passed to the Space.
This allows you to configure different configurations for different Processing Units.
Thus, having a Processing Unit Cluster point to a specific security directory.
It is possible to separate the security configurations from the Processing Unit configurations,
by placing the configurations in
/META-INF/spring/<Space name>-security.properties file.
The default Grid components security configuration file is
Here you can declare different configurations that will affect all the Grid components (such as GSA, GSM, GSC) together.
The default Web Management Console component security configuration file is
webui-security.properties. The configuration file affects only the Web Management Console.