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. 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. 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. Using Direct RDP or native SSH to access a remote system.Īs an alternative to using the default web‑based client, you can configure remote connections to use a local Windows-based client or native UNIX client.Using a native Windows client with the Remote Access Kit.Using the web to remote access a system.Privileged Access Service allows you to access remote systems in the following ways: You can capture and playback audited remote activity.You can configure authentication rules and authentication profiles for remote access.You can view session activity in the portal and in reports.You can watch and terminate remote sessions.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.
0 kommentar(er)
