Validating configurations

As a System Administrator, you can manage and validate the system configuration of certain Policy Server components from your home page. 

You can view your current configuration status and other parameters under the Home tab. This will be the first page displayed when you log in. 

This module verifies common issues and helps you take preventive measures to resolve them. 
Issues with errors will be listed first on this page. Appropriate resolution mechanisms and suggestions will also be displayed for each error. 

The available parameters are explained in brief below. Contact Seclore Support for more details. 

• License Consent: Checks whether license consent is required.
• SMTP Configuration: Checks whether the SMTP server is configured correctly. This is required for automated emails to be sent by the system, for example, during the new user onboarding process, when users request access to a file, or when the license is about to expire. 
• JCE (Java Cryptography Extension) Files:  Checks whether default JCE files are replaced with the files available in the Policy Server distribution package. If the files are not located in the specified location, data cannot be encrypted or decrypted by the Policy Server.
• Tomcat Java Options: Checks whether the Java options on the Tomcat server have been configured correctly. This includes parameters such as the JSP compilation parameter, time zone parameters, and the JNDI connection pool parameter. 
• Seclore Agent Installers:  Checks whether the installers for the Seclore for Windows are present at the appropriate locations. 
• Repository Email Suffix: Checks whether the email suffixes have been configured properly for different internal and external repositories.
• Policy Server URL Configuration:  Checks whether the primary and failover Policy Server URLs are configured correctly. These URLs are embedded in the header of every protected file. If only the primary URL is configured, then the file will not open if the URL is not reachable.
• Repository Mapping: Checks whether repositories have been mapped correctly. Incorrect configuration may result in users not being able to view other users of the same organization (e.g. while assigning permissions to them).
• Repository Initialization:  Checks whether a new added repository has been initialized correctly. Possible reasons why a repository may not be initialized include: invalid machine/port/login credentials for the LDAP server or being blocked by a firewall. 
• Auto Assign License Flag:  Checks whether the Automatic License Assignment option is enabled or disabled. This will display a warning if the feature is enabled for external repositories. 
• Server Port Configuration:  Checks whether more than one of three ports - HTTP, HTTPS, AJP - is open on the server. Opening more than one port could cause serious security issues and is not recommended. 
• Error Handling Configuration:  Checks whether the appropriate HTML error pages are present in the appropriate location on the server and whether the web.xml file is updated with the correct configuration. 
• Other Web Application: Checks whether other applications - apart from the Policy Server - are deployed in the same Tomcat server. 
• Favicon File:  Checks whether the default Tomcat favicon has been replaced with the Seclore lock icon file.