GET | List a remote session by [id]

  • 2 minute(s) read
Prev Next

Access information about a proxy session registered in PAM Core using the session id.

Requirements

  • Authorization with access permission to PAM Core.
  • Remote sessions started in PAM Core.

Request

Alert

To list a session by its id, the user must have access permission for Credentials and Devices in the authorization.

GET api/pam/session/remotesessions/[id]

Request Parameters

Info

The value of the id field is automatically assigned by Segura when the session is created and is obtained in the response of the request.

Parameter Type Required Description
id Integer Yes Unique identification code of the session.

Request Example

GET {{url}}/api/session/remotesessions/{id}

{
    "code": 200,
    "response": {
        "status": 200,
        "message": "",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "",
        "erro": false,
        "cod_erro": 0
    },
    "tenant": "Segura",
    "remote_session": [
        {
            "id": "30",
            "user": "MFASenhaSegura",
            "origin_ip": "172.16.20.158",
            "credential": "usrsudonopass",
            "device": "10.66.33.17:22",
            "protocol": "ssh",
            "proxy": "Web Proxy",
            "session_id": "df06257a1eb71ddf9e584d57a83a7eee9104dc43",
            "start": "2024-05-15 17:37:53",
            "end": "2024-05-15 17:38:00",
            "time": "00:00:07",
            "prevent_purge": "No",
            "request": null,
            "ITSM": null
        }
    ]
}

Response Body Fields

Info
  • The value for id is automatically assigned by the Segura platform when the session is created and should not be confused with the session_id parameter.
  • The session_id identifier is used internally by the application for session-related operations such as access control, activity tracking, and resource management. Each time a session is started, a new session_id is generated for that specific session.
Field Type Description Example
remote_sessions Array of objects Data of the listed remote sessions. -
id Integer Unique identification code of the remote session. -
user String Username used for authentication. -
origin_ip String IP address of the session's origin device. -
credential String Credential used to perform the session. -
device String Hostname or IP address of the destination device. -
protocol String Network protocol (SSH, RDP, HTTPS, among others). -
proxy String Type of proxy session. -
session_id String Unique hash generated by Segura to uniquely identify a specific session. e7acacb6aedbab70073456da5744166939b77527
start String Session start date and time in ISO 8601 format. 2024-05-06 16:05:07
end String Session end date and time in ISO 8601 format. 2024-05-06 16:07:59
time String Session duration. 00:02:52
prevent_purge String Indicates if automatic deletion of session data will occur. No
request String Request made by the user. -
ITSM String ITSM software code. -

Common Errors

HTTP Code Error Message Possible Cause Solution
400 Bad Request "1002: Session not found" Session not found. Check the id sent to search for the session and resend the request.
404 Not Found "Resource sub not found" The URL or requested resource is incorrect. Check the URL and resend the request.
500 Internal Server Error "Unexpected error." The error is on the server. Contact the support team for more information.
- Authorization Error "You are not authorized to access this resource" You do not have authorization to access this resource. Ask the administrator to review your access permission to PAM Core resources in A2A.
- Client authentication failed "Client authentication failed" Authentication failure of your application with the server. Check authentication parameters such as Access Token, Client ID, and Client secret and request a new access token.
- No route matched with those values "No route matched with those values" Missing authorization header in the API request. Request a new access token.
- Request timed out "Request timed out" The request time expired. Check connectivity between the request origin and the server.