> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/cyberark-aam-test-certificate-authentication.md).

# CyberArk AAM test certificate authentication

Test CyberArk AAM certificate authentication against the CCP REST API using a PowerShell script and a locally stored certificate thumbprint.

A REST API is an API that complies with the design principles of the REST, or Representational State Transfer, architectural style. REST APIs are therefore sometimes referred to as RESTful APIs.

A convenient way to test CyberArk's Rest API for AAM (Application Access Manager) is from ***Windows Powershell*** or ***Powershell ISE***.

```powershell
#Change location into your personal certificate store.
Set-Location "Cert:\CurrentUser\My\"

#Store the certificate with the thumbprint <your certificate thumbprint> in a variable ($Cert).
$Cert = Get-ChildItem | Where-Object {$_.Thumbprint -eq "<your thumbprint>"}

#Then the Invoke-RestMethod -Method Get...
Invoke-RestMethod -Method Get -Uri "<your Cyberark PasswordVault>AIMWebService/api/Accounts" -Certificate $cert -Body @{AppID = "<Your APP ID>"; Safe = "<Your Safe>"; Object = "<Object name>"}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/cyberark-aam-test-certificate-authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.