Click the  button to create a new Endpoint, or select an existing Endpoint by clicking on the desired row. Enter the required fields as defined in the table below.

...

To inactivate an endpoint click the Active link on the desired Endpoint, and it will toggle to Inactive. This will hide that Endpoint after leaving the screen, until the Active checkbox is unchecked. To reactivate an Enpoint, click the Inactive link and it will toggle back to Active. This endpoint is now active in the system again and ready for use.

...

It is typical to use the default file name and location to store the private key (which is in the .ssh subfolder of the user's home directory). You can optionally secure the private key file with a passphrase. It is an SSH requirement that the private key be readable only by its owner (e.g. oracle in the example above). So you must change the permissions accordingly (e.g. chmod 600 /home/oracle/.ssh/id_rsa). You will receive an error at connection time similar to the following if you omit this step.

Permissions 0777 for '/home/oracle/.ssh/id_rsa' are too open.

It is recommended that your private key files are NOT accessible by others otherwise private key will be ignored.

...

Validate that the derived name and location of the public key is correct, and enter the password for the Endpoint connection user (if not already provided on the Endpoint definition). Click the Upload button to upload the public key to the Endpoint.

Configure sudo user for Unix Operating System

FlexDeploy 4.6 supports use of sudo user for Unix Endpoint. FlexDeploy 4.5 patch release also supported sudo, but now configurations of sudo user is much simplified. Using this approach you can setup Endpoint with user "dan" but eventually sudo to user "oracle".

1. Set Endpoint user to the service account user. For example, dan.
2. Set the password for the Endpoint service account user.
3. Set the Run As (sudo) user. For example, oracle.
4. Ensure service account has same primary group as the user being sudoed to. i.e. dan and oracle user in this example should both have same Primary Group.
5. Add sudoers rule, such that service account can sudo to other user without prompting for a password.
   1. Test by executing following from terminal as service account – “sudo -u <user> bash -c whoami”
   2. It should print the run as user name without prompting for a password 
      Image Added
6. Delete the “Base Directory” on the physical endpoint server, if it was created with different user. FlexDeploy will recreate it on next connection. (Do not skip this step)
7. Click “Test Connection” on the Endpoint.

Special Note for Oracle Java Cloud Service

...