SpaceDeck - SSO IDP Setup

For configuring SSOClosed Single sign-on (SSO) is an authentication scheme that allows a user to log in with a single ID to any of several related, yet independent, software systems. (Secure Sign-On) for SpaceDeckClosed GigaSpaces intuitive, streamlined user interface to set up, manage and control their environment. Using SpaceDeck, users can define the tools to bring legacy System of Record (SoR) databases into the in-memory data grid that is the core of the GigaSpaces system., GigaSpaces supports using any IDPClosed An identity provider, or IDP, stores and manages users' digital identities. IDP and SSO can work together to authenticate users. that supports OpenID Connect (OIDCClosed OpenID Connect (OIDC) is an open authentication protocol that works on top of the OAuth 2.0 framework. Targeted toward consumers, OIDC allows individuals to use single sign-on (SSO) to access relying party sites using OpenID Providers (OPs), such as an email provider to authenticate their identities.) including Okta, Azure Active Directory, Amazon Cognito and Keycloak. We provide examples below of how to configure this using Okta and Azure Active Directory.

For user management through the IDP, roles and groups are created and then certain roles can be assigned to the user, for example admin. Via Spacedeck roles are then created with the same name which was created in the IDP and permissions are then assigned accordingly for each role.


  1. Create a developer account in Okta or Azure Active Directory.

  2. Once created, log in to the account and from the left side menu, select Applications:

  3. Click Create App Integration:

  4. From the pop-out menu, select Sign-in method OIDC - OpenID Connect and Application type Web Application. Then click Next:

  5. In the New Web App Integration screen:

    • Provide an App integration name. In the example below it is Test Demo App.

    • From Grant type select Authorization Code from the Client acting on behalf of a user section.

      If you want to use the refresh token mechanism, Refresh Token should also be selected.

    • From Sign-in redirect URIs set up a redirect URI -> URI to security service callback.

  6. Controlled access is customizable according to each client's requirements.  GigaSpaces has tested it with the following setting:

  7. Click Save. Okta will provide a Client ID and Client Secret.

  8. On the left side menu, select Security then API where you will find the Issuer URI that should be provided to SpaceDeck when you are setting up the IDP. Here the client has the option to customize and create a new authorization server. In this specific example, it was tested using the default:

  9. In the SpaceDeck, the Client ID, Client Secret and Issuer URI are populated as followed:

  10. To manager users in Okta, on the left side menu, select Directory then People:

  11. To manage groups in Okta (which are translated as roles in SpaceDeck), on the left side menu go to Directory then Groups. By default in Smart DIHClosed Smart DIH allows enterprises to develop and deploy digital services in an agile manner, without disturbing core business applications. This is achieved by creating an event-driven, highly performing, efficient and available replica of the data from multiple systems and applications, the role of ROLE_ADMIN has all privileges. It is customizable and can be changed via the config map.  However, to follow the default behavior and to use the ROLE_ADMIN in SMART DIHClosed Digital Integration Hub. An application architecture that decouples digital applications from the systems of record, and aggregates operational data into a low-latency data fabric., a ROLE_ADMIN group has to be created in OKTA and people assigned to this group.  This group will contain administrators and will have all privileges. To create a group in Okta, on the left side menu, go to Directory then Groups and click Add group, supply the name ROLE_ADMIN and then click Save.

  12. From the drop-down of Group source type, select Okta groups. The ROLE_ADMIN group will be in the list.

  13. To assign users to ROLE_ADMIN (or any other created group) on the left side menu, go to Directory then People and choose users from the list of users. Click the user. To switch the users groups, type the group name and then click enter.

  14. Now the access token claims have to be customized so it will have groups used in Smart DIH.  To accomplish this, on the left side menu go to Security then API and on the API screen, Authorization Servers:

  15. Select the server that is being used and go to the Claims tabs then Access:

  16. Click Add Claim and input a name for the Claim. In the Value type drop-down select Groups. For Filter, provide the filter to be applied. In this example, only groups with the ROLE_ prefix should be used. Click Create.

    The name of the claim will be used in SpaceDeck in the IDP Setup, for the setting of Authorization Grant Type

    In SpaceDeck:

  17. In order to bind the IDP that has been created above, the root user has to login to SpaceDeck with the correct username/password and then populate all the Connection fields in the Administration/General Setup menu.

    By default, the root user has root/password credentials.  This must be changed before installation using the parameter of global.password seen in step 3 of the Instructions for Smart DIH Installation using KubernetesClosed An open-source container orchestration system for automating software deployment, scaling, and management of containerized applications..

  18. Once the IDP has been configured, users can now use SSO login to sign in securely by selecting the Single sign-on option:

  19. After clicking LOGIN, the user will be redirected to the Okta login form to provide credentials:

  1. Login to your Azure developer account.

  2. Select Microsoft Entra ID:

  3. Select App registrations from the left-side menu:

  4. Click + New registration from the middle top:

  5. Input the following:

    1. Your application name

    2. Supported account types (can use the choice as per the screenshot below)

    3. Redirect URI - Select Web from the drop-down menu and provide the redirect URI of your application

    4. Click Register

  6. Select App registrations and select the App you have just registered. In the example below, this is named Test App:

  7. Click Add a certificate or secret from the right-hand side in order to create a client secret:

  8. Click + New client secret:

  9. Provide a secret description and select an expiration time from the drop-down menu. Then click Add which is found at the bottom of the screen:

  10. Once a client secret has been created, copy and save the Value of the secret:

    It is important to copy and save the value as you will NOT be able to view it later

  11. The Client secret value should be pasted into the Client Secret field in the SpaceDeck Administration/General Setup menu during IDP setup:

  12. From the Azure application, copy the for Application (client) id:

  13. The Application (client) ID value should be pasted into the Client Id field in the SpaceDeck Administration/General Setup menu during IDP setup:

  14. From the Azure application, select Endpoints from the middle top menu:

  15. From the Endpoints list, find and copy the link OpenID Connect metadata document that ends with /v2.0/.well-known/openid-configuration. Paste this link into a browser and copy the issuer value from the response. This value should then be pasted into the Issue URL field in the SpaceDeck Administration/General Setup menu during IDP setup:

  16. Generate scope:

    1. From the Azure application, select Expose an API

    2. Click Add next to Application ID URI.  You can use the default value. At the bottom of the screen, click Save.

    3. Click +Add a scope

    1. Provide a Scope name

    2. For Who can consent? select Admins and users

    3. Populate the mandatory fields with your description, then click Add scope at the bottom of the screen.

  17. Copy the Scopes value:

  18. This Scopes value should then be pasted into the scope field in the SpaceDeck Administration/General Setup menu during IDP setup:

  19. To manage roles for your application (in this case SpaceDeck), go to the Azure application and select App roles and then click + Create app role:

  20. Provide role details and then click Apply at the bottom of the screen. This is an example of a role creation for ROLE_ADMIN:

  21. To manage users for your application (in this case SpaceDeck), navigate to the Microsoft Entra ID screen and from the left-side Manage menu, select Users:

  22. To assign users and groups (roles) for your application (in this case SpaceDeck), navigate to Microsoft Entra ID screen and select Enterprise applications from the left-side menu:

  23. Select your application and then on the next screen, click Assign Users and Groups:

  24. Click Add user/group:

  25. Select user and role and click Assign at the bottom of the screen:

  26. In the SpaceDeck, in the Administration/Role Management menu enter roles for the Authorization Grant Type field: