NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automate NetBackup utilities
- Scheduling utilities to run automatically
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- Custom parameters
- Performance profile schedule customization
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Data retention periods for SDK database objects
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
AD/LDAP Configuration for authentication and authorization
To configure AD/LDAP for user authentication as well as authorization, Portal Administrator must create at least one User Group in portal which is also present in AD/LDAP as a UserGroup.
- Login to Portal as a SuperUser, navigate to Admin > User Groups.
- Create a new user group with the same group name present in AD/LDAP. Only members of this user group can access the portal when
ldap.authorization
is set to TRUE inportal.properties
. - Assign appropriate privileges to the newly created user group. See Setting user group privileges section in the User Guide.
- Record the domain name where new users will be created.
To find domain name, navigate to Admin - Domains > Domain Name. This will be required during LDAP configuration in
portal.properties
. - In case Portal server is unable to resolve AD/LDAP hostname, add an entry into the
/etc/hosts
file on the Portal server<AD_IP_ADDRESS> <AD_DOMAIN_NAME> For example: 192.168.2.90 ad.gold
- Back up the portal's configuration file located at:
Linux:
/opt/aptare/portalconf/portal.properties
Windows:
C:\opt\aptare\portalconf\portal.properties
- On the portal server, update the
portal.properties
file with the configuration settings mentioned below:Linux:
/opt/aptare/portalconf/portal.properties
Windows:
C:\opt\aptare\portalconf\portal.properties
ldap.enabled=true ldap.context=com.sun.jndi.ldap.LdapCtxFactory ldap.searchBase=<AD_SEARCHBASE> ldap.url=ldap://<AD_URL>:389 ldap.dn=<AD_USER_ACCOUNT_HAVING_PRIVILEGE_TO_SEARCH_IN_AD> ldap.password=<PASSWORD_FOR _USER_MENTIONED_IN_ldap.dn> ldap.loginAttribute=<AD_ATTRIBUTE_TO_SEARCH_USER> ldap.authorization=true ldap.newUserDomain=example.company.com
- To change the existing superuser LDAP_ID to map to the AD username, update the existing record on the Oracle database server.
For example: If the login attribute is user_name and actual value is Admin, update the existing record as below:
# sqlplus portal/<portal_password>@scdb # UPDATE ptl_user SET ldap_id = 'Admin' WHERE user_id = 100000; # commit;
Use this updated username to login to the external directory, instead of aptare. Since the user account aptare (user_id=100), is an internal bootstrap user, it is required to maintain referential integrity among database tables and therefore you must avoid using aptare for external LDAP integration.
Note:
The user_id = 100000 is always the default user_id for the super user account.
- Restart the portal Tomcat service.
On Linux run:
# /opt/aptare/bin/tomcat-portal restart
In Windows environment, use the Windows Services Console to locate and restart the Portal Tomcat service.
- Login to the portal using any user present in the Active Directory and part of the group created in step 2.
Note that to automatically create a user in the portal, these attributes must be set for each user in AD/LDAP:
givenName: Mandatory. It is used as the first name of the user.
telephoneNumber: Optional
mobile: Optional
mail: Mandatory
Note:
If for any reason the LDAP configuration is disabled from the portal, the portal administrator must set the password for all the AD/LDAP users in portal.