Uploaded image for project: 'InsightEdge Platform'
  1. GS-13318

When the secured XAP Manager is initialized, it does not start and requests the default security.properties file

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 12.2
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      00011393
    • Workaround:
      See description, add security.properties with default security manager implementation
    • Acceptance Test:
      manual
    • Sprint:
      12.2-RC1
    • Product:
      XAP
    • Edition:
      Premium

      Description

      Expected Behavior:
      When security is enabled, the XAP Manager should initialize without requiring any manual intervention.

      Actual Behavior:
      The REST component doesn't start, and generates the following error:
      [manager][1/40252] 2017-08-29 16:49:13,960 REST SEVERE [ScalatraBootstrap] - Failed to create security manager; Caused by: com.gigaspaces.security.SecurityException: Failed to load security properties file....
      Caused by: java.io.FileNotFoundException: Could not locate resource [null] or the default [security.properties] in the classpath or under [config/security/] directory.

      Workaround:
      Add .../config/security/security.properties file with the following content:
      com.gs.security.security-manager.class=com.gigaspaces.security.fs.FileSecurityManager

      Note: In the FileSecurityManager class, the default file is: security/gs-directory.fsm.


        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: