- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7.2 Installation using non-root user
We are in process of to installing 7.2 (Software Bundle) with remote database option.
From installation guide - It appear to be only 'oracle' is allowed by the installation process. If we wish to use a non-root username other than 'oracle' username and primary group 'oinstall'. Has anyone tried it before and are there any known issues/limitations?
for e.g
-- user
aveksa for oracle
--group
avksagrp for oinstall
Note:
1. root installation is not an option
2. service accounts 'oracle' and group 'oinstall' are owned by database teams.
- Tags:
- 7.2
- 7.2 Enablement Hub
- Enablement
- Enablement Hub
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- Install
- non-root
- oracle
- release 7.2
- remote database
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
- Version 7.2
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IGL 7.2 software bundle installer has been improved as noted in the release notes. The only options are to install as root or oracle user. Here's a quote from RSA Identity Governance and Lifecycle 7.2.0.x Release Notes:
Installer
There are several improvements to the RSA Identity Governance and Lifecycle installation process:
- The installation process has been improved to allow installation using either the root user or oracle user, depending on the specific environment and requirements.
Installation as the root user is required for deployments in which you use an RSA-supplied database or in which you want to run RSA Identity Governance and Lifecycle as a service. Root user installation is required for any deployment in which sudo functionality is needed.
Installation as the oracle user is an option for environments that use a remote database and do not require the use of services or sudo functionality.
For instructions for each of these installation options, see the RSA Identity Governance and Lifecycle Installation Guide.
- The installation script now prompts users to confirm passwords entered when configuring a remote database.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IGL 7.2 software bundle installer has been improved as noted in the release notes. The only options are to install as root or oracle user. Here's a quote from RSA Identity Governance and Lifecycle 7.2.0.x Release Notes:
Installer
There are several improvements to the RSA Identity Governance and Lifecycle installation process:
- The installation process has been improved to allow installation using either the root user or oracle user, depending on the specific environment and requirements.
Installation as the root user is required for deployments in which you use an RSA-supplied database or in which you want to run RSA Identity Governance and Lifecycle as a service. Root user installation is required for any deployment in which sudo functionality is needed.
Installation as the oracle user is an option for environments that use a remote database and do not require the use of services or sudo functionality.
For instructions for each of these installation options, see the RSA Identity Governance and Lifecycle Installation Guide.
- The installation script now prompts users to confirm passwords entered when configuring a remote database.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There’s room for improvement, for IGL installation with remote database option. It does not make sense to use 'oracle' , 'oinstall' groups to run installer,
For a non-root user installation - the installer should pretty much allow any user/group to perform installation.
I voted the Idea.
