Virtual Appliance's users. Do we have ROOT user access into VAPP?

Products

• CA Identity Suite
• CA Identity Manager
• CA Identity Portal
• CA Identity Governance

Issue/Introduction

What are the available VAPP users clients have access to?

How can we log into VAPP as the superuser, or ROOT, user?

Environment

Virtual Appliance 14.x

Resolution

In a Virtual Appliance environment, we have four possible users available for clients to access and administer their VAPP deployment.  These users are described in the documentation link Switching Users 

config is the default user for VAPP ssh console access. 
dsa is the CA Directory user. 
imps is the Provisioning Server user
oracle is the Oracle database user
Note: The Oracle user is available only when you deploy VAPP in Demo or Sandbox mode, using the embedded Oracle XPress database.

Broadcom has sole custody of the credentials for the ROOT user.   Broadcom considers this proprietary information and will not share or assist with accessing VAPP as the ROOT user.    
There are other users (shown below) who are also considered internal proprietary data and are not available for end-user access. 

root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
games:x:12:100:games:/usr/games:/sbin/nologin
ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin
nobody:x:65534:65534:Kernel Overflow User:/:/sbin/nologin
systemd-coredump:x:999:997:systemd Core Dumper:/:/sbin/nologin
dbus:x:81:81:System message bus:/:/sbin/nologin
tss:x:59:59:Account used for TPM access:/:/sbin/nologin
sssd:x:998:995:User for sssd:/:/sbin/nologin
chrony:x:997:994:chrony system user:/var/lib/chrony:/sbin/nologin
sshd:x:74:74:Privilege-separated SSH:/usr/share/empty.sshd:/sbin/nologin
systemd-oom:x:992:992:systemd Userspace OOM Killer:/:/usr/sbin/nologin
rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin
rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin
tcpdump:x:72:72::/:/sbin/nologin
apache:x:48:48:Apache:/usr/share/httpd:/sbin/nologin
postfix:x:89:89::/var/spool/postfix:/sbin/nologin
config:x:2000:2000::/home/config:/bin/bash
oracle:x:2001:2001::/u01/app/oracle:/bin/bash
imps:x:2002:2002:IMPS Administrator:/opt/CA/IdentityManager/ProvisioningServer:/bin/bash
wildfly:x:2003:2003::/home/wildfly:/sbin/nologin
jboss:x:2004:2004::/home/jboss:/sbin/nologin
dsa:x:2005:2005:DXserver Administrator:/opt/CA/Directory/dxserver:/bin/bash

 

 

 

Additional Information

There are some situations and problems which result in the VAPP permissions needing to be reset.  Any condition that requires the permissions to be updated will require a patch from the support organization.   That patch will only correct the permissions and return them to our design specifications, we will not give a patch that will increase access to these specific users.