Advanced settings

# The URL of eureka service
eureka.client.serviceUrl.defaultZone=http://localhost:8761/eureka/

# The URL of the latest Conpliance Checker knowledge base file: 
common.autoUpdateUrl=https://dl.chemaxon.com/cchecker/cc-database.jar 
#The URL of the latest cHemTS knowledge abase file
common.htsAutoUpdateUrl:https://dl.chemaxon.com/hts/hts-knowledge-base.jar

# The URL of the text file containing the version of the latest Compliance Checker knowledge base file.
common.autoUpdateVersionUrl=https://dl.chemaxon.com/cchecker/cc-version.txt 
#The URL of the text file containing the version of the latest cHemTS knowledge base file
common.htsAutoUpdateVersionUrl:https://dl.chemaxon.com/hts/hts-version.txt

common.autoUpdateEnabled=true

# Enables to schedule the knowledge base update automatically.
# The value should be a cron-like expression, which extends the usual UN*X definition to include triggers
# on the second as well as minute, hour, day of month, month and day of week.
# Example patterns:
# "0 0 * * * *" = the top of every hour of every day.
# "*/10 * * * * *" = every ten seconds.
# "0 0 8-10 * * *" = 8, 9 and 10 o'clock of every day.
# "0 * 6,19 * * *" = 6:00 AM and 7:00 PM every day.
# "0 0/30 8-10 * * *" = 8:00, 8:30, 9:00, 9:30 and 10 o'clock every day.
# "0 0 9-17 * * MON-FRI" = on the hour nine-to-five weekdays
# "0 0 0 25 12 ?" = every Christmas Day at midnight
common.autoUpdateScheduler=0 0 0 * * MON-FRI
# Enables to schedule the cHemTS knowledge base update automatically.
#common.htsAutoUpdateScheduler=0 0 1 * * MON-FRI

# You can map user groups to ROLEs in CC and cHemTS by this setting.
 # CC ROLES - We have 5 CC Roles
 # User groups can be mapped to the following Roles:
 # - USER: Can execute Single and File checks - against all Countries and those User-defined category groups
 # which are not restricted for the USER by the CONTENT_MANAGER or by the ADMIN.
 # - EXPERT_USER: Can execute Single and File checks - against all Countries and those User-defined category groups
 # which are not restricted for the EXPERT_USER by the CONTENT_MANAGER or by the ADMIN.
 # - CONTENT_MANAGER: Has limited access to the Administration functions:
 #   -- User-defined category group editor: Select categories and make restrictions for the USER and/or EXPERT_USER roles,
 #   -- User-defined category editor
 #   -- Database update history
 #   -- Report template editor
 # - ADMIN: Has access to all administration functions
 # cHemTS ROLES - We have 3 cHemTS Roles
 # - HTS_USER: Can execute cHemTS Single and File checks
 # - HTS_CONTENT_MANAGER : Can execute Single and File checks and has limited access to the Administration functions: -- Report template editor
 # - HTS_ADMIN : Has access to all administration functions.
 # COMMON ROLES
 # - SYSTEM: A special group to run automatic system checks
 # CC and cHemTS roles can be combined, so for example a user could have both USER and HTS_USER roles.
 # For automated system communication we need to have a SYSTEM user that can log in to the services.
 # The SYSTEM user - with very limited privileges - will use one of the authentication providers 
 # mentioned below, so you must register it in your LDAP / AD server.
     common.systemUser=system
     common.systemPassword=system

 # Roles - with special privileges - can be assigned to different user groups:
     common.rolesToGroupsMap={"userGroups":[],"userPattern":".*","adminGroups":["cc-admin"],"adminPattern":"","contentManagerGroups":["cc-content-manager"],"contentManagerPattern":"","expertUserGroups":["cc-expert-user"],"expertUserPattern":"","systemGroups":["cc-system"],"htsAdminGroups":["hts-admin"],"htsAdminPattern":"","htsContentManagerGroups":["hts-content-manager"],"htsContentManagerPattern":"","htsUserGroups":["hts-user"],"htsUserPattern":"","systemPattern":""}

 # Configuring ROLES
 # - FOR LDAP
 # If you use LDAP, then you can set it's configuration like this: 
 #   {"servers":[{"serverUrl":"ldap://ldap.server.com:389/dc=test,dc=tld","userDNPatterns":["uid={0},cn=users,cn=accounts"],"groupSearchBase":"","managerDN":"uid=cchecker,cn=sysaccounts","managerPassword":"<password>"}]}
 # This is a standard JSON but it has to be in one line. The "servers" property references an array. In this array you can set as many LDAP servers as you want. 
 # These servers will be checked in this specified order, and the first LDAP server that can authenticate the user will authenticate it.
 # The properties stands for the following:
 # "serverURL" -- The URL of the LDAP server
 # "userDNPatterns" -- The domain name of the users in the LDAP tree
 # "groupSearchBase" -- Domain name of groups in LDAP tree
 # "managerDN' -- The domain name of the manager user to query LDAP tree.
 # "managerPassword" -- The password of manager user.
     common.ldapConfig = {"servers":[{"serverUrl":"ldap://ldap.server.com:389/dc=test,dc=tld","userDNPatterns":["uid={0},cn=users,cn=accounts"],"groupSearchBase":"","managerDN":"uid=cchecker,cn=sysaccounts","managerPassword":"<password>"}]}

 # - FOR ACTIVE_DIRECTORY
 # If you use ACTIVE_DIRECTORY, then you can set you can set it's configuration like this: 
 #   {"servers":[{"domain":"your.domain","url":"ldap://server.domain.com"}]}
 # This is a standard JSON but it has to be in one line. The "servers" property references an array. 
 # In this array you can set as many Active Directory servers as you want. 
 # These servers will be checked in this specified order, and the first AD server that can authenticate the user will authenticate.
     common.activeDirectoryConfig={"servers":[{"domain":"your.domain","url":"ldap://server.domain.com"}]}

 # - FOR IN_MEMORY
 # If you are using IN_MEMORY authentication manager, you can configure it like this:
 #   {"users":[{"name":"<user>","password":"<userpwd>","roles":["USER"]}, {"name":"<admin>","password":"<adminpwd>","roles":["ADMIN"]}, {"name":"contentmanager", "<password>": "<contentmanagerpwd>", "roles":["CONTENT_MANAGER"]}, {"name":"expertuser", "<password>": "<expertuserpwd>", "roles":["EXPERT_USER"]}, {"name":"system","<password>":"system","roles":["SYSTEM"]}]}
 # This is a standard JSON but it has to be in one line. The "servers" property references an array. 
     common.inMemoryConfig = {"users":[{"name":"user","password":"password","roles":["USER"]},{"name":"admin","password":"adminPass","roles":["ADMIN"]},{"name":"contentmanager","password":"password","roles":["CONTENT_MANAGER"]},{"name":"expertuser","password":"password","roles":["EXPERT_USER"]},{"name":"system","password":"system","roles":["SYSTEM"]},{"name":"hts_user","password":"hts_password","roles":["HTS_USER"]},{"name":"hts_admin","password":"hts_adminPass","roles":["HTS_ADMIN"]},{"name":"hts_contentmanager","password":"hts_password","roles":["HTS_CONTENT_MANAGER"]}]}

 # - DIRECT ROLE ASSIGN
 # Roles can be assigned directly to special users by setting the value of the config key.
 # The value should be a comma separated list of ROLES. 
 # Currently available roles are: USER, EXPERT_USER, CONTENT_MANAGER, ADMIN, SYSTEM.
#   roles.<username>=<roles>

# The default view for Regulation Categories. Valid values are: COUNTRIES, CHECK_LEVELS
#check.default.regulationCategories=CHECK_LEVELS

# Setting this to true will only display the check levels as selectable categories on the check pages
#check.hideCountries=true

# The default report format for batch checks. Valid values are: HTML,PDF,SDF,MRV,XLSX
#batch.default.reportFormat=HTML

# Comma separated list of fields to be included in the JSON reports.

# Including only needed fields in JSON reports can greatly increase the speed of report generation

# To include child fields, parent fields also have to be listed

# If none of the listed fields are present in the result or the config key is not set
# then the full result will be added to the report

# Example: 
# [ 
#    [
#       { 
#          "segments":[ 
#             { 
#                "categoryName":"catName", 
#                "categoryCode":1234 
#             } 
#          ], 
#          "inputProperties":{ 
#             "ID":"123", 
#             "Name":"Name" 
#          } 
#       } 
#    ] 
# ] 

#
 To include only the categoryCode and ID in the JSON report from the above example result 
# the following configuration has to be made: 
#json.report.fields=segments,categoryCode,inputProperties,ID

report.xlsx.max-image-count=10000

# Enables to schedule the removal of all check related data from the database.
# The value should be a cron-like expression, which extends the usual UN*X definition to include triggers
# on the second as well as minute, hour, day of month, month and day of week.

# Example patterns:
# "0 0 * * * *" = the top of every hour of every day.
# "*/10 * * * * *" = every ten seconds.
# "0 0 8-10 * * *" = 8, 9 and 10 o'clock of every day.
# "0 * 6,19 * * *" = 6:00 AM and 7:00 PM every day.
# "0 0/30 8-10 * * *" = 8:00, 8:30, 9:00, 9:30 and 10 o'clock every day.
# "0 0 9-17 * * MON-FRI" = on the hour nine-to-five weekdays
# "0 0 0 25 12 ?" = every Christmas Day at midnight
#batch.cleanup.scheduler=0 0 4 * * *

hts.search.mixture.ignorablefragments.included=[...]
hts.search.mixture.ignorablefragments.excluded=[...]

hts.search.mixture.ignorablefragments.excluded=Br,CC(O)=O

hts.search.mixture.ignorablefragments.included=SC#N;acidic

{
    "servers" : [{
            "serverUrl" : "ldap://ldap1.mycompany.com/dc=mycompany,dc=com",
            "userDNPatterns" : ["uid={0},cn=users,dc=mycompany,dc=com", "uid={0},cn=external,dc=mycompany,dc=com"],
            "groupSearchBase" : "",
            "groupSearchFiler" : "",
            "userSearchBase" : "",
            "userSearchFilter" : "",
            "managerDN" : "uid=admin,cn=sysusers,dc=mycompany,dc=com",
            "managerPassword" : "PASSWORD!",
            "root" : ""
        }, {
            "serverUrl" : "ldaps://ad.mycompany.com/dc=cmp,dc=com",
            "userDNPatterns" : [],
            "groupSearchBase" : "",
            "groupSearchFiler" : "",
            "userSearchBase" : "dc=cmp,dc=com",
            "userSearchFilter" : "sAMAccountName={0}",
            "managerDN" : "Administrator@cmp.com",
            "managerPassword" : "other_PASSWORD!",
            "root" : "dc=cmp,dc=com"
        }
    ]
}

{
    "servers" : [{
            "serverUrl" : "ldap://ldap1.mycompany.com/dc=mycompany,dc=com",
            "userDNPatterns" : ["uid={0},cn=users,dc=mycompany,dc=com", "uid={0},cn=external,dc=mycompany,dc=com"],
            "managerDN" : "uid=admin,cn=sysusers,dc=mycompany,dc=com",
            "managerPassword" : "PASSWORD!"
        }, {
            "serverUrl" : "ldaps://ad.mycompany.com/dc=cmp,dc=com",
            "userSearchBase" : "dc=cmp,dc=com",
            "userSearchFilter" : "sAMAccountName={0}",
            "managerDN" : "Administrator@cmp.com",
            "managerPassword" : "other_PASSWORD!",
            "root" : "dc=cmp,dc=com"
        }
    ]
}

{"servers" : [{"serverUrl" : "ldap://ldap1.mycompany.com/dc=mycompany,dc=com", "userDNPatterns" : ["uid={0},cn=users,dc=mycompany,dc=com", "uid={0},cn=external,dc=mycompany,dc=com"], "managerDN" : "uid=admin,cn=sysusers,dc=mycompany,dc=com", "managerPassword" : "PASSWORD!"}, { "serverUrl" : "ldaps://ad.mycompany.com/dc=cmp,dc=com", "userSearchBase" : "dc=cmp,dc=com","userSearchFilter" : "sAMAccountName={0}", "managerDN" : "Administrator@cmp.com", "managerPassword" : "other_PASSWORD!", "root":"dc=cmp,dc=com"}]}

{
    "servers": [
        {
            "domain" : "first.domain",
            "url" : "ldap://first.com"
        } ,
        {
            "domain" : "second.domain",
            "url" : "ldap://second.com"
        } 
    ]
}

// Don't forget that you have to set it in the <code>application.properties</code> file in one line.
// Like this: { "servers": [    {"domain" : "first.domain", "url" : "ldap://first.com"} , {"domain" : "second.domain", "url" : "ldap://second.com"} ]}
// We only used multi line example for better readability.

eureka.instance.non-secure-port-enabled=false
eureka.instance.secure-port-enabled=true
security.require-ssl=true
# The format used for the keystore
server.ssl.key-store-type=<format>
# The path to the keystore containing the certificate
server.ssl.key-store=<path to jks file>
# The password used to generate the certificate
server.ssl.key-store-password=<password>
# The alias mapped to the certificate
server.ssl.key-alias=<alias>