Documentation

Development

User Acquisition

Monetization

Industry

Self-Hosted Deployment

Amazon Web Services

Microsoft Azure

On premises

vpctl

Self-Hosted Deployment

​
​
Self-Hosted Deployment
  • Overview
  • Amazon Web Services
  • Microsoft Azure
  • On premises
    • Release notes
    • Installation
      • Infrastructure overview
      • Hardware requirements
      • Prerequisites
      • Deployment
      • Postdeployment
        • Set up the identity subsystem
      • Costs
    • Maintenance
  • Administration
  • Security
  • vpctl
  1. Self-Hosted Deployment (previously called Unity Virtual Private Cloud)
  2. Self-Hosted Deployment on-premises
  3. Installation

Set up the identity subsystem

Set up the identity subsystem, based on Keycloak
Read time 1 minute
Last updated a month ago

Unity Virtual Private Cloud includes an identity provider and broker component based on Keycloak. Keycloak includes these major capabilities:
  • Authentication and authorization
  • Storage of information about users and service accounts keys
Keycloak is included in the above deployment, but you must perform customer-specific postdeployment and administration tasks.

1. Access Keycloak

Access the Keycloak admin console at
https://<your-domain>/auth
.

Change the default admin credentials

The keycloak admin credentials are static and aren't tied to any identity provider.
When you sign in for the first time, change the default admin credentials:
  1. In the Keycloak admin console, switch to the default realm, that is, the master realm.
  2. Go to Users, and then select the
    admin
    user.
  3. On the Credentials tab, select Reset password.
  4. Enter a new password.
  5. Turn off Temporary.
  6. Record the credentials somewhere secure.

2. Complete the setup of the identity subsystem

To complete the setup of the identity subsystem, ensure that you are signed in to Keycloak, and then go to the unity realm.

2.1 Set up the URI properties for the dashboard client

To redirect the browser back to the frontend after a successful sign-in, add a valid redirect URI.
  1. Go to Manage > Clients, and then select the dashboard client.
  2. On the Settings tab, modify these values:
    • Set Root URI to
      https://<solution-domain-name>
      .
    • Set Valid redirect URIs to
      https://<solution-domain-name>/*
      .
  3. Select Save.

3. Perform administration tasks

  1. Complete the initial solution onboarding.
  2. If required, set up single sign-on (SSO) for the identity subsystem.
  3. If you don't use SSO, then create users in Keycloak.
  4. Grant user access to the organization.
  5. Optionally, configure monitoring integration in parallel or later.
After you have completed these steps, users can access the application.

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page
    • 1. Access Keycloak

      • Change the default admin credentials

    • 2. Complete the setup of the identity subsystem

      • 2.1 Set up the URI properties for the dashboard client

    • 3. Perform administration tasks


Report a problem with this page
​
​