5.6 Printing Deployment Details

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

Note:

Assuming the sandbox environment, the URL's will use the <WEB_HOST>. If using a load balancer in front of OHS, it will use the <LBR_HOST>. 
############################OAA Deployment Details: START###################################
OAAService=https://ohs.example.com/oaa/runtime
AdminUrl=https://ohs.example.com/oaa-admin/index.html
PolicyUrl=https://ohs.example.com/oaa-policy
SpuiUrl=https://ohs.example.com/oaa/rui
Email=https://ohs.example.com/oaa-email-factor
Push=https://ohs.example.com/oaa-push-factor
Fido=https://ohs.example.com/fido
SMS=https://ohs.example.com/oaa-sms-factor
TOTP=https://ohs.example.com/oaa-totp-factor
YOTP=https://ohs.example.com/oaa-yotp-factor
KBA=https://ohs.example.com/oaa-kba
RELEASENAME=oaainstall
# Key below is Base64 encoded API key
oaaapikey=cGFzc3dvcmQ=
# Key below is Base64 encoded Policy API key
oaapolicyapikey=cGFzc3dvcmQ=
# Key below is Base64 encoded Factor API key
oaafactorapikey=cGFzc3dvcmQ=
############################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://ohs.example.com/oaa-admin/index.html
PolicyUrl=https://ohs.example.com/oaa-policy
RISK=https://ohs.example.com/risk-analyzer
RISKCC=https://ohs.example.com/risk-cc
RELEASENAME=oaainstall
# Key below is Base64 encoded Policy API key
oaapolicyapikey=cGFzc3dvcmQ=
# Key below is Base64 encoded Factor API key
riskfactorapikey=cGFzc3dvcmQ=
############################Deployment Details: END###################################
For OUA installations, the DRSS Deployment Details are also printed on the console:
#####DRSS Deployment Details: START##### 
DRSS=https://ohs.example.com/oaa-drss 
RELEASENAME=oaainstall 
# Key below is Base64 encoded DRSS API key 
drssapikey=cGFzc3dvcmQ=
####################Deployment Details: END#####################
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/index.html The administrator username, oaaadmin. <password> set in OAM OAuth identity store.
Self-Service Portal SpuiUrl https://<hostname.domain>:<port>/oaa/rui

Username from OAM OAuth identity store.

The username must exist in 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/index.html 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

<RELEASENAME> can be in lowercase.

<Base64Decoded(oaapolicyapikey)>
OAA Runtime OAAService https://<hostname.domain>:<port>/oaa/runtime <RELEASENAME>-oaa

<RELEASENAME> can be in lowercase.

<Base64Decoded(oaaapikey)>
Risk RISK https://<hostname.domain>:<port>/risk-analyzer <RELEASENAME>-risk

<RELEASENAME> can be in lowercase.

<Base64Decoded(riskfactorapikey)>
Risk Customer Care RISKCC https://<hostname.domain>:<port>/risk-cc <RELEASENAME>-risk-cc

<RELEASENAME> can be in lowercase.

<Base64Decoded(riskfactorapikey)>
KBA KBA https://<hostname.domain>:<port>/oaa-kba

<RELEASENAME>_OAA_KBA

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

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, for example oaainstall-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 for Oracle Universal Authenticator