Summary: Customize security to meet your application requirements
OverviewGigaSpaces XAP security was designed with customization in mind - since there are numerous security standards and practices, users can either use the built in security features in the product or customize them to their own needs. The following security aspects can be customized:
Packaging and ClasspathThe most common scenario is for all services to share the same custom security. This is easily accomplished by placing the custom implementation classes in the lib/optional/security directory.
<GigaSpaces root>/lib/optional/security/my-custom-security.jar Processing units may share a custom security implementation that may differ from that of the GSM and GSCs. In this case, the custom security jar can be placed under pu-common. <GigaSpaces root>/lib/optional/pu-common/my-pu-custom-security.jar If each processing unit has its own custom security implementation, the custom security jar can be part of the processing unit distribution. <GigaSpaces root>/deploy/hello-processor/lib/my-processor-custom-security.jar
|
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |