Does the Red Hat Single Sign-On (RH SSO) Operator supports using 'SealedSecret' objects to create the default 'admin' user?

Solution Verified - Updated -

Issue

After configuring a SealedSecret as Secret/credentials-<CR>, the RH SSO Operator is unable to create the keycloak pods with the following error message:

{"level":"info","ts":<TIMESTAMP>,"logger":"action_runner","msg":"(    0)     FAILED Update Keycloak admin secret : Object <NAMESPACE>/credential-<CR> is already owned by another SealedSecret controller <CONTROLLER>"}

Environment

  • Red Hat Single Sign-On (RH SSO)
    • 7.X (Operator)
  • Red Hat OpenShift Container Platform (OCP)
    • 4.X

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content