> For the complete documentation index, see [llms.txt](https://docs.blusapphire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blusapphire.io/log-forwarding/03_log-forwarding-guide/log-forward/iraje-pam.md).

# Iraje PAM

**IRAJE PAM LOG INTEGRATION**

*Client Prerequisites & Integration Guide*

Iraje PAM → REST API → BluSapphire Collector → SIEM Platform

## **Overview**

Iraje Privileged Identity Management (PAM) provides ready-to-use REST APIs that allow a SIEM to pull its event logs. This guide lists what must be done on the client side in Iraje PAM, Active Directory and the network, and which details must be shared with BluSapphire so the integration can be completed and tested.

### **Prerequisites:**

• Administrator access to the Iraje PAM dashboard.

• Active Directory administrator access (or help from the AD team) to identify or create a service account.

• Ability to modify firewall rules between the BluSapphire log collector and the Iraje PAM server.

• Iraje PAM version that exposes the /api/windowsevents and /api/irajeevents endpoints (confirm with Iraje support if unsure).

## **Part 1 — Prepare the API Service Account**

Iraje PAM APIs use Basic authentication with an Active Directory username and password. There is no separate API key or token to generate. The account created here is the credential BluSapphire will use.

**Step 1. Identify or create a dedicated AD account**

* Create a dedicated, non-interactive Active Directory user for SIEM log collection, for example svc-blusapphire-siem.
* Note the login name in the format **@**, where is the AD username and is the corporate domain.

**Step 2. Add the same user in Iraje PAM**

* Log in to the Iraje PAM dashboard as an administrator.
* Open the user management section and add the AD user created in Step 1 as an Iraje PAM user. The username must match the AD accounvt.

**Step 3. Grant access to the Reports module**

* Assign the user a role or permission that gives access to the Reports module in the Iraje PAM dashboard.

**NOTE:** The API account must be configured in Iraje PAM and must have Reports module access. Without this, the account cannot retrieve logs even if the AD password is correct. Menu names may differ slightly between Iraje PAM versions; refer to the Iraje PAM administrator guide or Iraje support if a label does not match.

**Step 4. Confirm the account is usable**

* Confirm the AD account is enabled and not locked, and that its password policy is known (expiry and rotation). If the password expires, BluSapphire must be given the new password each time it changes.

## **Part 2 — Network and Certificate Readiness**

**Step 1. Confirm the Iraje PAM URL and port**

* The APIs are served at **https\://\<PAM\_url>\[:\<custom\_port>]**. Confirm whether a custom port is used.

**Step 2. Allow access from the BluSapphire collector**

* Allow inbound HTTPS (TCP) from the BluSapphire log collector IP to the Iraje PAM server on the PAM port.
* If a reverse proxy, WAF or load balancer sits in front of PAM, make sure the /api/ paths are permitted through it.

**Step 3. Provide the TLS certificate if it is not publicly trusted**

* If the PAM certificate is issued by an internal CA or is self-signed, share the CA (public) certificate in .pem or .crt format so the collector can validate the connection.

**NOTE:** Share only the public certificate.

## **Part 3 — Verify API Access (Recommended)**

Before handing over the details, the client can confirm the API works from any machine that can reach the PAM server.

**Step 1. Test the Iraje event logs API**

* Run the following command, replacing the placeholders:

**curl -u '@:' 'https\://\<PAM\_url>\[:\<custom\_port>]/api/irajeevents?beforeSeconds=3600'**

**Step 2. Check the result**

* Success: HTTP 200 with a JSON response. An empty list is valid if no events occurred in the last hour.
* If the call fails, see Part 6 — Common Issues.
* Alternatively, use Postman: create a GET request, choose Basic Auth with the @ and password, and add beforeSeconds as a query parameter.

## **Part 4 — Information to Share with BluSapphire**

Once the steps above are complete, please send the following details to the BluSapphire team. Share the password through a secure channel only, not in plain email.

<table data-header-hidden><thead><tr><th width="79.0859375"></th><th width="185.57421875"></th><th width="215.140625"></th><th></th></tr></thead><tbody><tr><td><strong>#</strong></td><td><strong>Item</strong></td><td><strong>Example / Format</strong></td><td><strong>Remarks</strong></td></tr><tr><td>1</td><td>Iraje PAM base URL</td><td>https://PAM.example.com</td><td>URL reachable from the BluSapphire collector</td></tr><tr><td>2</td><td>Port</td><td>443 or custom port</td><td>Only if not the default HTTPS port</td></tr><tr><td>3</td><td>API username</td><td>svc-blusapphire-siem@corp.example.com</td><td>Format: @</td></tr><tr><td>4</td><td>API password</td><td>(shared securely)</td><td>AD password of the account</td></tr><tr><td>5</td><td>CA certificate</td><td>.pem or .crt file</td><td>Only if internal CA or self-signed</td></tr><tr><td>6</td><td>Reports module access</td><td>Confirmed: Yes / No</td><td>For the account in item 3</td></tr><tr><td>7</td><td>Firewall access</td><td>Confirmed: Yes / No</td><td>From the BluSapphire collector IP to the PAM port</td></tr></tbody></table>

## **Part 5 — Common Issues**

| **Symptom**                          | **Likely cause**                                                       | **Action**                                                                          |
| ------------------------------------ | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| HTTP 401 Unauthorized                | Wrong password, or username not in @ format                            | Re-check the username format and password; confirm the AD account is not locked     |
| HTTP 403 Forbidden or no data access | Account lacks Reports module access, or is not configured in Iraje PAM | Complete Part 1, Steps 2 and 3                                                      |
| Connection timed out                 | Firewall blocks the collector, or wrong port                           | Re-check Part 2, Steps 1 and 2                                                      |
| Certificate error                    | Internal CA or self-signed certificate                                 | Provide the CA certificate as described in Part 2, Step 3                           |
| Empty list returned                  | No events in the time window                                           | Increase beforeSeconds or generate a test event (for example a PAM dashboard login) |
