Global settings
| Administration Page | Application/Contract | Syracuse/Collaboration | Class | Settings | Representation | Setting |
|---|
| General settings | Authentication | Proxy settings | Mailer |
| License | Logs | Patch | Synchronization |
In this section, a pivot date must be provided to define the century used by default when the date is 2 digits.
Two fields, upper and lower bound, are present in this section. Only the upper bound is entered, the lower bound is calculated accordingly.
For example, if you enter 2029 for the upper bound:
* Any date with a year on two digits that is smaller or equal to 29 will be in the [2000-2029] range.
* All the dates with a year on two digits between 30 and 99 will be in the [1930-1999] range, which is the reason that 1930 > is displayed in the lower bound.
In this section, a default authentication setting can be defined for all users who have standard authentication. The different fields that must be filled are the following:
Authentication
It can be Basic, OAuth2, SAML2.
- Basic authentication sends the password to the server. This is possible for users whose credentials are stored in the database or in an LDAP server. Both the login name and the password field are case sensitive.
- OAuth2 requires an OAuth2 server which handles all authorization.
- SAML2 requires a SAML2 identity provider which handles all authorization.This authentication will be taken when the user has "default" authentication method. A user specific authentication method takes precedence. In any case, the user will have to select the correct authentication method from the login screen.
Default LDAP server
An LDAP server can be entered if Basic authentication is selected.
Default OAuth2 server
An OAuth2 server can be entered if OAuth2 authentication is selected.
Default SAML2 identity provider
A SAML2 identity provier can be entered if SAML2 authentication is selected.
When a user has a version 7 page containing a widget that accesses an external URL such as www.google.com, the proxy settings of the web browser apply to allow or not access to this external URL.
However, when a version 7 process wants to directly access an external URL, for example, when calling a web service, it is necessary to set up the proxy server that will be used. This section allows you to set up the proxy settings for the current Syracuse server. The following information must be entered:
Proxy
If this check box is selected, a proxy configuration is used to access the external services.
Default proxy configuration
This field refers to the Administration reference Proxy configuration used.
This section defines a default mailer that will be used for notifications.
This section allows entering a percentage value that will apply on the maximum size granted by the license for a given period for web service transfer. Every time this percentage is reached, a notification will automatically be sent. The description of the notification is given at the following set-up page, for the record called license_web_warn.
This section allows changing parameters of the log system. The web server platform includes a logging system producing logs that can be sent upon request to Sage, thus easing diagnoses in case of troubleshouting. Every time the server starts, a new log file is created in which the system will write the traces. The log files produced are generated with a limited size. When this size is reached, the log file is closed, automatically compressed, and a new file is created. Only the most recent files are kept in the system, and the set-up allows to define the corresponding policy:
Maximum number of files
Defines the maximum number of log files that will be kept. When a new file is created, the oldest files will be deleted if the number of log files present exceeds this limit.
Maximum size
Defines the maximum size if a log file. This size refers to a not compressed file; the space required on disk to store the file is significantly lower than the size given here. When the current log file reaches the size, it is closed, compressed, and a new file is created.
Maximum number of days
Defines a maximum number of days a log file will be stored in the system.
This indicator is automatically updated by the platform. When set to active, it means that patches cannot be applied. The main reason is that a patch application is in progress, or that a following step (the integrity check, triggered after patch application) is still running.
As this information is temporarily stored in the mongoDB database because node.js needs to be automatically restarted during these phases, it might be possible that the lock remains set even if the patch application and the additional phases are finished. If this happens, the user can manually unlock the system by modifying this field; which has to be done carefully after having checked that everything is right.
The information located in this block is related to future extensions for the platform (SData synchronization) and must not be modified at this time.