- Centrify putty download how to#
- Centrify putty download install#
- Centrify putty download download#
- Centrify putty download windows#
By default, the log file log.txt is found in the Program Data\Centrfy\CPS Run Log folder. For more information about specifying URLs for trusted websites and the success or failure of the operation, see the client launcher log file. If you attempt to add a trusted website and don’t see confirmation that the operation was successful, it might indicate that there is a security issue, such as invalid or expired credentials. You can remove a trusted website for the client launcher by manually editing the registry entry on the computer that hosts the local client. If the URL isn't listed but the user specifies it is a trusted website, the client launcher requests additional login details (REST call: GetLoginDetails) from the server and passes the login details to a local client-such as PuTTY or a remote Session Host-to connect to the target system. The client launcher checks the \HKEY_CURRENT_USER\Software\Centrify\CpsRun\HostWhiteList registry key to determine whether the URL is listed as a trusted website. The server returns the authentication token, which is cached by the Admin Portal, and sent with the login information and current URL to the client launcher. The following diagram illustrates the basic flow when you use a local Windows-based client with the client launcher.Īs illustrated in the diagram, selecting a target and account for remote access in the Admin Portal sends initial login information and the request for a token to the server that handles process requests (REST call: GetAuthToken). You can add other host names to the list of trusted websites or remove host names from the list to ensure the arguments used to invoke the local client are only passed from the secure websites that you trust. This information is stored the HostWhiteList registry key on the computer that hosts the local Windows-based client.
Centrify putty download download#
If you download the Remote Access Kit and trust the website detected for the current cloud server, Privileged Access Service adds the host name for the current cloud server to a list of trusted websites for launching the local client. The Remote Access Kit enables you to execute the command to open the local client and pass arguments to it without manually typing the command and its arguments every time you open a new session.
Centrify putty download install#
If you decide to use a local Windows-based client for remote connections, you have the option to download and install a separate "client launcher" application that is part of the Remote Access Kit software package. For information about adding the gateway service to a connector, see Selecting connector services.
Centrify putty download how to#
For information about how to use a native UNIX client for remote connections, see Using Direct RDP or native SSH to access a remote system. For information about how to configure a local Windows-based client instead of the default web-based browser for remote connections, see Selecting user preferences. If the gateway service is available for a connector in your infrastructure and you have appropriate permissions, you can log on either by using stored account information or by manually specifying a user name and password. However, these clients and remote connections still require you to enable the SSH or RDP gateway service for at least one connector before you can log on remotely to target systems using secure shell or remote desktop sessions. By configuring remote connections to use a local Windows-based client or a native client, you can use a familiar interface you are comfortable with for performing remote operations.
Centrify putty download windows#
Privileged Access Service allows you to access remote systems in the following ways:
Logging on to a target system through the connector has several advantages. Both of these options enable you to log on to the target system from the Admin Portal through the Centrify Connector. You can also configure remote sessions to start by launching a local Windows client with an appropriate command or a direct RDP or SSH configuration file. By default, if you have the View and Login permissions, you can log on to remote systems from the Admin Portal using the default web browser-based client.