![Novell Sentinel Rapid Deployment 6.1 Installation Manual Download Page 52](http://html1.mh-extra.com/html/novell/sentinel-rapid-deployment-6-1/sentinel-rapid-deployment-6-1_installation-manual_1711906052.webp)
52
Sentinel 6.1 Rapid Deployment Installation Guide
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
Server Installation
The Sentinel 6.1 Rapid Deployment Server installation creates a
novell
system user and novell
group that own the installed files within the
<
install_directory
>
. If the user does not exist, it is
created and its home directory is set to
/home/novell
. If a new user is created, the password for the
user is not set by default in order to maximize security. If you want to log in to the system as the
novell user, you must set a password for the user after installation.
Collector Manager Installation
Linux:
The installer prompts you to specify the name of the system user who will own the installed
files, as well as the location to create its home directory. By default, the system user is
esecadm
;
however, you can change this system username. If the user does not exist, it is created along with its
home directory. If a new user is created, the password for the user is not set by default to maximize
security. If you want to log in to the system as the user, you must set a password for the user after
installation.The default group is
esec
.
During the client installation, if the user already exists, the installer does not prompt for the user
again. This behavior is similar to the behavior during uninstallation or reinstallation of software. If
you want the installer to prompt for the user again:
1
Delete the user and group created at the time of first installation
2
Clear the environment variables ESEC_USER from
/etc/profile
Windows:
No users are created.
The password policies for system users are defined by the operating system that is being used.
5.2.2 Sentinel Application and Database Users
All Sentinel 6.1 Rapid Deployment application users are native database users and their passwords
are protected by using procedures followed by the native database platform. These users have only
read access to certain tables in the database so that they can execute queries against the database.
The admin user is the administrator user for all Sentinel applications to login.
By default the following database users are created during installation:
The dbauser is created as a superuser who can manage the database. The password for the dbauser is
accepted at the time of installation. This password is stored in the
<user home directory>/
.pgpass
. The system follows the PostgreSQL database password policies.
The appuser is the non-superuser that is used by the Sentinel applications to connect to the database.
By default, the appuser uses a password that is randomly generated during installation, and is stored
encrypted in the
<
Install_directory
>/config
container xml files (
das_core.xml
,
das_binary.xml
, etc.). To change the password for the appuser, use the
<install_directory>/
bin/dbconfig
utility.
NOTE:
There is also a postgreSQL database user that owns the entire database including system
database tables. By default, the postgres database user is set to NOLOGIN so that no one can login
as the postgreSQL user.
Summary of Contents for Sentinel Rapid Deployment 6.1
Page 4: ...4 Sentinel 6 1 Rapid Deployment Installation Guide novdocx en 17 September 2009 ...
Page 8: ...8 Sentinel 6 1 Rapid Deployment Installation Guide novdocx en 17 September 2009 ...
Page 22: ...22 Sentinel 6 1 Rapid Deployment Installation Guide novdocx en 17 September 2009 ...
Page 72: ...72 Sentinel 6 1 Rapid Deployment Installation Guide novdocx en 17 September 2009 ...
Page 78: ...78 Sentinel 6 1 Rapid Deployment Installation Guide novdocx en 17 September 2009 ...