Getting Started


This topic provides a high-level explanation of the XAP security mechanisms, so you can start working with them quickly.

Layers of Security

XAP security can be applied in three separate layers:

  • The data layer, which includes Space and Processing Units.
  • The grid layer, which includes grid components (GSA, GSM, GSC, XAP Manager + RESTful API).
  • The transport layer, which provides a generic network filter with SSL support.

You may secure any of these, or all of them for maximum security.

Configuring Security

Security is configured using a property file that includes required and custom properties. For more information, refer to the following parts of the Security section in this Administration guide:

Enabling Security

Security can be enabled separately for the data layer and the grid layer.

  • The data layer has options to declare a secured Space or Processing Unit.
  • The grid layer has options to declare the Grid as secured.

Security Implementations for Licensed GigaSpaces Products

Note

The Open Source editions do not include a security implementation. A reference implementation is provided instead.

When no property file is configured, there is a fallback implementation mainly used for testing or to get you started. This implementation stores the user credentials in a local file and can be used to demonstrate that security has been applied.

Refer to the following sections for more information about XAP security implementation:

Hello World Example

The Hello World example will guide you step by step into deploying Processing-Unit with a secured Space, accessing it from a remote proxy, and declaring principals using the administration tools.

Spring Security

Spring Security is one of the most mature and widely used Spring projects. We provide a Spring-based security bridge to enable a pluggable implementation into various authentication sources. One such example is with LDAP (Lightweight Directory Access Protocol).

For more information, refer to Spring Security Bridge.