Configuration and Administration
glog.security Properties
To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.
Note: To protect hosted systems, these properties cannot be modified in the cloud without a service request.
|
Property |
New in Version |
Definition |
|---|---|---|
| glog.security.basicAuth.on | 25C | Controls HTTP Basic Authentication for all types of application HTTP requests. |
| glog.security.basicAuth.type.Rest.on | 25C | Controls HTTP Basic Authentication for Rest types of application HTTP requests. |
| glog.security.basicAuth.type.Servlet.on | 25C | Controls HTTP Basic Authentication for Servlet types of application HTTP requests. |
| glog.security.basicAuth.useCase.api.on | 25C | Controls HTTP Basic Authentication for api application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.data-int.on | 25C | Controls HTTP Basic Authentication for data-int application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.BatchCSVUtilServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.BatchCSVUtilServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.DBXMLServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.DBXMLServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.DirLoadServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.DirLoadServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.ExternalSystemServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.ExternalSystemServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.TransformerServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.TransformerServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.glog.integration.servlet.WMServlet.on | 25C | Controls HTTP Basic Authentication for glog.integration.servlet.WMServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.gtm.integration.aes.servlet.AESFilingResponseServlet.on | 25C | Controls HTTP Basic Authentication for gtm.integration.aes.servlet.AESFilingResponseServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.gtm.integration.itm.servlet.ITMIntegrationServlet.on | 25C | Controls HTTP Basic Authentication for gtm.integration.itm.servlet.ITMIntegrationServlet application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.int-api.on | 25C | Controls HTTP Basic Authentication for int-api application use cases of HTTP requests. |
| glog.security.basicAuth.useCase.resources-int.on | 25C | Controls HTTP Basic Authentication for resources-int application use cases of HTTP requests. |
| 23C |
Enables the synchronization of BI Roles to IDCS Groups from OTM to IDCS during user synchronization. See Synchronize Users (Legacy). Default: false |
|
|
Note: The functionality of this property is disabled. If it was enabled by Oracle, it would allow you to use another domain for your VPD context. It defaults to false. |
||
| glog.security.stackTrace.hide | See the Security Guide. | |
| 21C |
Fixes problems with custom security on agents and recurring processes conflicting with internal impersonation. Set to true to address the issue. Default: False |
|
| 21A |
Allows users to be created in IDCS. Default: true. See Synchronize Users (Legacy). |
|
| 21A |
Allows users to be deleted in IDCS. Default: false. See Synchronize Users (Legacy). |
|
| glog.security.user.idcs.allowUpdate | 24A | Allows users to be updted in IDCS. Default: false. See Synchronize Users (Legacy). |
| 21A |
Enables the auto-synchronization from OTM to IDCS during User Maintenance. Default: false. See Synchronize Users. |
|
| 21A |
The allowed length of the Email Address for IDCS synchronization. It is not recommended to change this property. Default: 100. See Synchronize Users. |
|
| 21A |
Set up the External System for IDCS and configure this property to specify the IDCS external system. No default. See Synchronize Users. |
|
| 21A |
The allowed length of the First Name for IDCS synchronization. It is not recommended to change this property. Default: 100. See Synchronize Users. |
|
| 21A |
The allowed length of the Last Name for IDCS synchronization. It is not recommended to change this property. Default: 100. See Synchronize Users. |
|
| 21A |
The allowed length of the User Name for IDCS synchronization. It is not recommended to change this property. Default: 100. See Synchronize Users. |
|
| 21A |
Enables the various validations on the user attributes fields which are synchronized between OTM and IDCS. Disabling the validation can cause Bad Request Errors coming from IDCS. It is not recommended to change this property. Default: true. See Synchronize Users. |
|
|
To enable navigation from Oracle Transportation Management to Transportation Intelligence without an external single sign on (SSO) solution, set this property to "true". The default is false. |
Related Topics
Configuring Oracle Identity Cloud Service User Synchronization
