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
To configure AD/LDAP only for user authentication, the portal administrator must create users in the NetBackup IT Analytics Portal similar to those present in AD/LDAP database.
- Login to the NetBackup IT Analytics Portal as a super user and go to Admin > Users.
- Create a new user with the same user name present in AD/LDAP.
- Assign appropriate privileges to the new user.
- If the portal server fails to resolve the AD/LDAP hostname, add the hostname entry in 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.properties
configuration file of the portal from:On Linux:
/opt/aptare/portalconf/portal.properties
On Windows:
C:\opt\aptare\portalconf\portal.properties
- Update the
portal.properties
configuration file of the portal with the following configurations: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=false #ldap.newUserDomain=
- 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.
Linux: /opt/aptare/bin/tomcat-portal restart
Windows: Use the Windows Services Console to locate and restart the portal Tomcat service.
- Login to the portal using any user name common across AD/LDAP and the NetBackup IT Analytics Portal.