The default behavior in the job scheduler is to use a non-secure HTTP connection with the Grid Execution Environment (GEE) to manage how jobs are run. If you want to make a secure HTTP connection between application servers, then you must create a job scheduler custom property to enable such communication.
When the job scheduler custom property is defined, the job scheduler discovers the inbound SSL configuration assigned to the GEE application servers. The inbound SSL configuration assigned to the GEE servers is used as the outbound SSL configuration in the job scheduler.
The job scheduler discovers the GEE SSL configuration by looking at the SSL inbound transport channel assigned to the HTTPS port. If there is no SSL configuration defined at the transport channel level, the job scheduler looks at the application server level. If not found at the application server level, the job scheduler looks at the GEE node level. If not found at the GEE level, the job scheduler uses the default SSL configuration defined at the cell level.