Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 3. Managing Cluster Credentials

Perform tasks to manage authentication for Data Grid clusters.

Prerequisites

  • An oc client in your $PATH.

3.1. Retrieving Cluster Credentials
Copy link

You can retrieve credentials for your Data Grid clusters as base64-encoded strings from secrets in your cluster namespace.

If you do not create secrets and credentials when you create clusters, the Data Grid Operator automatically generates them with the following defaults:

Default usernames
  • Management user is admin.
  • Application user is developer.
Default credentials secrets
  • example-rhdg-mgmt-generated-secret contains credentials for the management user.
  • example-rhdg-app-generated-secret contains credentials for the application user.

Procedure

  • Get the credentials from the secret. For example, to get the password for the application user from the default secret: 

    $ oc get secret example-rhdg-app-generated-secret \
-n my_namespace -o jsonpath="{.data.password}" | base64 --decode
    Copy to Clipboard Toggle word wrap
    Tip

    Use the jp JSON processor to retrieve credentials as follows: 

    $ oc get secret example-rhdg-app-generated-secret \
-n my_namespace -o json | jq '.data | map_values(@base64d)'

{
  "password": "tUElqbfoJmT,NJVN",
  "username": "developer"
}
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top