Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1307

Use default hostnames for SSO clients in RHPAM OpenShift templates

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 7.4.0.GA
    • 7.0.1.GA
    • Cloud
    • OpenShift

    • CR1
    • Hide
      1. Start OpenShift
      2. Import SSO image stream and sso secret from application-templates application-templates
      3. Deploy SSO template (e.g. sso72-https.json)
      4. Import RHPAM image stream and secrets
      5. Deploy RHPAM template with SSO (e.g. rhpam70-authoring.yaml) without custom hostnames
      Show
      Start OpenShift Import SSO image stream and sso secret from application-templates application-templates Deploy SSO template (e.g. sso72-https.json) Import RHPAM image stream and secrets Deploy RHPAM template with SSO (e.g. rhpam70-authoring.yaml) without custom hostnames
    • 2019 Week 20-22

      Connection to the RH-SSO can be configured in the RHPAM templates. In the template we specify the name of the client in RH-SSO realm. If this client is not in the RH-SSO realm, then a new one is auto created.
      New client require custom hostnames to specify the URLs in client for the redirection. When custom hostname is not provided, new client is not created and deployment of the Business central and deployment of the Kie Server fail.

      If BUSINESS_CENTRAL_HOSTNAME_HTTP, BUSINESS_CENTRAL_HOSTNAME_HTTPS EXECUTION_SERVER_HOSTNAME_HTTP or EXECUTION_SERVER_HOSTNAME_HTTPS is not specified, then should be used default hostnames for the SSO clients (BUSINESS_CENTRAL_SSO_CLIENT and KIE_SERVER_SSO_CLIENT)

      Changes should be applied to for all templates with SSO configuration.

              rhn-support-zanini Ricardo Zanini
              jakubschwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: