Validate a Basic SSO Flow using WebGate Registration

In this section you validate single-sign on works to the OAM Kubernetes cluster via Oracle WebGate. The instructions below assume you have a running Oracle HTTP Server (for example ohs_k8s) and Oracle WebGate installed on an independent server. The instructions also assume basic knowledge of how to register a WebGate agent.

Note: At present Oracle HTTP Server and Oracle WebGate are not supported on a Kubernetes cluster.

Update the OAM Hostname and Port for the Loadbalancer

If using an NGINX ingress with no load balancer, change {LOADBALANCER-HOSTNAME}:${LOADBALANCER-PORT} to {MASTERNODE-HOSTNAME}:${MASTERNODE-PORT} when referenced below.

  1. Launch a browser and access the OAM console (https://${LOADBALANCER-HOSTNAME}:${LOADBALANCER-PORT}/oamconsole). Login with the weblogic username and password (weblogic/<password>)

  2. Navigate to ConfigurationSettings ( View )Access Manager.

  3. Under Load Balancing modify the OAM Server Host and OAM Server Port, to point to the Loadbalancer HTTP endpoint (e.g and <port> respectively). In the OAM Server Protocol drop down list select https.

  4. Under WebGate Traffic Load Balancer modify the OAM Server Host and OAM Server Port, to point to the Loadbalancer HTTP endpoint (e.g and <port> repectively). In the OAM Server Protocol drop down list select https.

  5. Click Apply.

Register a WebGate Agent

In all the examples below, change the directory path as appropriate for your installation.

  1. Run the following command on the server with Oracle HTTP Server and WebGate installed:

    $ cd <OHS_ORACLE_HOME>/webgate/ohs/tools/deployWebGate
    $ ./ -w <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8s -oh <OHS_ORACLE_HOME> -ws ohs

    The output will look similar to the following:

    Copying files from WebGate Oracle Home to WebGate Instancedir
  2. Run the following command to update the OHS configuration files appropriately:

    $ cd <OHS_ORACLE_HOME>/webgate/ohs/tools/setup/InstallTools/
    $ ./EditHttpConf -w <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8s -oh <OHS_ORACLE_HOME>

    The output will look similar to the following:

    The web server configuration file was successfully updated
    <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8s/httpd.conf has been backed up as <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8s/httpd.conf.ORIG   
  3. Launch a browser, and access the OAM console. Navigate to Application SecurityQuick Start WizardsSSO Agent Registration. Register the agent in the usual way, download the configuration zip file and copy to the OHS WebGate server, for example: <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8/webgate/config. Extract the zip file.

  4. Copy the Certificate Authority (CA) certificate (cacert.pem) for the load balancer/ingress certificate to the same directory e.g: <OHS_DOMAIN_HOME>/config/fmwconfig/components/OHS/ohs_k8/webgate/config.

    If you used a self signed certificate for the ingress, instead copy the self signed certificate (e.g: /scratch/ssl/tls.crt) to the above directory. Rename the certificate to cacert.pem.

  5. Restart Oracle HTTP Server.

  6. Access the configured OHS e.g, and check you are redirected to the SSO login page. Login and make sure you are redirected successfully to the home page.

Changing WebGate agent to use OAP

Note: This section should only be followed if you need to change the OAM/WebGate Agent communication from HTTPS to OAP.

To change the WebGate agent to use OAP:

  1. In the OAM Console click Application Security and then Agents.

  2. Search for the agent you want modify and select it.

  3. In the User Defined Parameters change:

    a) OAMServerCommunicationMode from HTTPS to OAP. For example OAMServerCommunicationMode=OAP

    b) OAMRestEndPointHostName=<hostname> to the {$MASTERNODE-HOSTNAME}. For example

  4. In the Server Lists section click Add to add a new server with the following values:

    • Access Server: Other
    • Host Name: <{$MASTERNODE-HOSTNAME}>
    • Host Port: <oamoap-service NodePort>

    Note: To find the value for Host Port run the following:

    $ kubectl describe svc accessdomain-oamoap-service -n oamns

    The output will look similar to the following:

    Name:                     accessdomain-oamoap-service
    Namespace:                oamns
    Labels:                   <none>
    Annotations:              <none>
    Selector:                 weblogic.clusterName=oam_cluster
    Type:                     NodePort
    IP Families:              <none>
    Port:                     <unset>  5575/TCP
    TargetPort:               5575/TCP
    NodePort:                 <unset>  30540/TCP
    Endpoints:      ,
    Session Affinity:         None
    External Traffic Policy:  Cluster
    Events:                   <none>

    In the example above the NodePort is 30540.

  5. Delete all servers in Server Lists except for the one just created, and click Apply.

  6. Click Download to download the webgate zip file. Copy the zip file to the desired WebGate.

  7. Delete the cache from <OHS_DOMAIN_HOME>/servers/ohs1/cache and restart Oracle HTTP Server.