4.7 Printing Deployment Details

After the deployment completes, the following information is printed on the console.

Note:

In cases where you install the ingress controller that ships with OAA, the host and port is set to the worker node where the controller gets installed. In cases where you are using your own ingress controller, assuming a basic setup, the host and port is set to the value of the property install.global.serviceurl in installOAA.properties.

In cases where ingress is disabled, the host and NodePort of the worker nodes are printed.

############################OAA Deployment Details: START###################################
OAAService=https://oaainstall-host/oaa/runtime
AdminUrl=https://oaainstall-host/oaa-admin
PolicyUrl=https://oaainstall-host/oaa-policy
SpuiUrl=https://oaainstall-host/oaa/rui
Email=https://oaainstall-host/oaa-email-factor
Push=https://oaainstall-host/oaa-push-factor
Fido=https://oaainstall-host/fido
SMS=https://oaainstall-host/oaa-sms-factor
TOTP=https://oaainstall-host/oaa-totp-factor
YOTP=https://oaainstall-host/oaa-yotp-factor
KBA=https://oaainstall-host/oaa-kba
RELEASENAME=oaainstall
# Key below is Base64 encoded API key
oaaapikey=YXBpa2V5dG9iZXNldGR1cmluZ2luc3RhbGxhdGlvbgo=
# Key below is Base64 encoded Policy API key
oaapolicyapikey=cG9sYXBpa2V5dG9iZXNldGR1cmluZ2luc3RhbGxhdGlvbgo=
# Key below is Base64 encoded Factor API key
oaafactorapikey=ZmFjdG9yYXBpa2V5dG9iZXNldGR1cmluZ2luc3RhbGxhdGlvbgo=
############################Deployment Details: END###################################
For OAA-OARM, OARM, and OUA installations, the Risk Deployment Details are also printed on the console:
############################Risk Deployment Details: START###################################
AdminUrl=https://oaainstall-host/oaa-admin
PolicyUrl=https://oaainstall-host/oaa-policy
RISK=https://oaainstall-host/risk-analyzer
RISKCC=https://oaainstall-host/risk-cc
RELEASENAME=riskinstall
# Key below is Base64 encoded Policy API key
oaapolicyapikey=cG9sYXBpa2V5dG9iZXNldGR1cmluZ2luc3RhbGxhdGlvbgo=
# Key below is Base64 encoded Factor API key
riskfactorapikey=cmlza2ZhY3RvcmFwaWtleXRvYmVzZXRkdXJpbmdpbnN0YWxsYXRpb24K
############################Deployment Details: END###################################
For OUA installations, the DRSS Deployment Details are also printed on the console:
#####DRSS Deployment Details: START##### 
DRSS=https://oaainstall-host/oaa-drss 
RELEASENAME=oaainstall 
# Key below is Base64 encoded DRSS API key 
drssapikey=ZHJzc2FwaWtleXRvYmVzZXRkdXJpbmdpbnN0YWxsYXRpb24= 
####################Deployment Details: END#####################

Note:

For OUA deployments, after printing the above, if you see the following error deploying OUA integration agents, you can ignore it and move to the Post Installation Steps section:
Assurance Level was not created correctly. Please check if the Policy Snapshot has been
      applied correctly.
If you ever need to reprint the deployment information:
  1. Enter a bash shell for the OAA management pod if not already inside one:
    kubectl exec -n <namespace> -ti <oaamgmt-pod> -- /bin/bash
    For example:
    kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7d7597c694-vn4ds -- /bin/bash
  2. Run printOAADetails.sh to print the deployment details:
    cd ~/scripts
    ./printOAADetails.sh -f settings/installOAA.properties

    Note:

    This will use the installOAA.properties in the <NFS_CONFIG_PATH>.

Based on the information printed for the deployment, the consoles can be accessed as follows:

Console Print Details Reference * URL Username Password
Administration Console AdminUrl https://<hostname.domain>:<port>/oaa-admin The administrator username, for example oaadmin

Note:

The Administrator username must have been added to the OAA-Admin-Role group. See Creating Users and Groups in the LDAP Store.
<password> set in OAM OAuth identity store.
Self-Service Portal SpuiUrl https://<hostname.domain>:<port>/oaa/rui Username from OAM OAuth identity store.

Note:

The username must have been added to the OAA-App-User group. See Creating Users and Groups in the LDAP Store.
<password> set in OAM OAuth identity store.

* Throughout this documentation the value in the Print Details Reference column is used to denote the URL to use. For example: "Launch a browser and access the <AdminURL>", refers to accessing the corresponding URL https://<hostname.domain>:<port>/oaa-admin shown.

Based on the information printed for the deployment, the REST API endpoint information is as follows:

REST API Print Details Reference ** URL Username ** Password **
OAA/OARM Admin PolicyUrl https://<hostname.domain>:<port>/oaa-policy <RELEASENAME>-oaa-policy <Base64Decoded(oaapolicyapikey)>
OAA Runtime OAAService https://<hostname.domain>:<port>/oaa/runtime <RELEASENAME>-oaa <Base64Decoded(oaaapikey)>
Risk RISK https://<hostname.domain>:<port>/risk-analyzer <RELEASENAME>-risk <Base64Decoded(riskfactorapikey)>
Risk Customer Care RISKCC https://<hostname.domain>:<port>/risk-cc <RELEASENAME>-risk-cc <Base64Decoded(riskfactorapikey)>
KBA KBA https://<hostname.domain>:<port>/oaa-kba <RELEASENAME>_OAA_KBA

Note:

The <RELEASENAME> must be all uppercase. If <RELEASENAME> contains “-“, then replace with “_”. for example oaa-install translates to : OAA_INSTALL_OAA_KBA.
<Base64Decoded{ oaafactorsapikey}>
DRSS DRSS https://<hostname.domain>:<port>/oaa-drss <RELEASENAME>_OAA_DRSS

Note:

The <RELEASENAME> must be all uppercase. If <RELEASENAME> contains “-“, then replace with “_”. for example oaa-install translates to : OAA_INSTALL_OAA_DRSS.
<Base64Decoded(drssapikey)>

** Throughout this documentation, when REST API examples are given, the value in the Print Details Reference column is used to denote the URL to use, and the values in the Username and Password columns represent the username and password to use.

For example:
curl --location -g --request POST '<OAAService>/preferences/v1' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic <Base64Encoded(<username>:<password>)>' 
etc...
<OAAService> refers to accessing the corresponding URL https://<hostname.domain>:<port>/oaa/runtime, and <username> refers to <RELEASENAME>-oaa, and <password> refers to <Base64Decoded(oaaapikey)>.
For more information about using the above details to access REST APIs, see:

Next Steps: Post Installation Steps.