---
title: RPAM Portal
slug: kronpam-reference-guide-3-9-0/rpam-portal
description: Learn how the Kron PAM Remote Access Portal, a user-friendly web portal, enables secure remote access and device management for third-party vendors on an internal network. With SSH and RDP protocol support, streamline your network operations effortlessly.
docTags: 
createdAt: 2023-09-26T11:13:10.306Z
---

The **RPAM Portal** is a web-based access layer designed to serve privileged users, such as third-party contractors or remote employees, who require controlled access to internal corporate systems. This component is deployed outside the corporate internal network, either within a Demilitarized Zone (DMZ) or in an environment provided by a Cloud Service Provider (CSP).

Operating as the primary entry point for remote privileged access, the RPAM Portal enables users to connect securely to internal systems within predefined working hours and according to access policies enforced by the Kron PAM platform. Since the RPAM Portal is built on a VPN-less access model, it does not require VPN client software or VPN management components on user endpoints.

A secure HTTPS-based tunnel is established between the **RPAM Portal** and the **RPAM Connector**. This tunnel replaces traditional VPN connectivity by providing encrypted communication channels while reducing compatibility issues, minimizing endpoint dependencies, and improving overall security posture.

See the [End User Guide](docId\:JAD8bri2JszZ_oY26EIdd) for more information. 

:::hint{type="info"}
The system administrator can check the RPAM Portal version by executing the following command:

**java -jar rpam-0.0.1-SNAPSHOT.jar -v**

The example output:

07:54:47.776 \[main] INFO com.kron.sc.rap.GitInfoService --

branch: merge/sc-3.9.0
:::

:::hint{type="info"}
The RPAM Portal logs various types of operational and security-related information, including JWT token verification details, login page errors, authentication and MFA events, device search and connection request/response activities, HTTP error codes, and error messages generated by the PAM system. These logs are stored in files on the RPAM Portal and can be recorded at different log levels.

Supported log levels are **error, warn, info, verbose, and debug**. The **debug** level provides the most detailed information, while the **error** level contains only critical issues. The log level can be configured using the **log.level.remote.access** parameter in the **application.properties** file located at **/pam/remote-access-portal/conf.**

Log file rotation is controlled by the **log.time.rotation.remote.access** parameter to prevent log files from growing excessively large. The supported rotation options include **1 day, 3 days, 1 week, 2 weeks, 1 month, 3 months, no rotation.**

The default values are:

- log.level.remote.access: **info** 
:::