> 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/da/knowledge-base/troubleshooting-articles/test-secret-server-access-with-a-powershell-script.md).

# Test adgang til Secret Server med et PowerShell-script

Brug et PowerShell-script til at teste klientens forbindelse til REST API'en for Delinea Secret Server og bekræfte, at søgninger efter hemmeligheder virker uden for Remote Desktop Manager.

Når en post af typen ***Delinea Secret Server*** ikke kan godkende eller ikke returnerer nogen hemmeligheder, viser en test af forbindelsen uden for Remote Desktop Manager, om problemet kommer fra arbejdsstationen, netværket eller Secret Server-kontoen. Remote Desktop Manager kommunikerer med Secret Server via dens REST API. Den anmoder om et OAuth2-token fra `<Secret Server URL>/oauth2/token` og forespørger derefter `<Secret Server URL>/api/v1/secrets`. Følgende PowerShell-script udfører de samme to kald.

1. Gem koden nedenfor i en fil med navnet `searchsecret.ps1`.
2. Erstat værdierne for `$url`, `$username`, `$password` og `$domain` med Deres Secret Server-URL og legitimationsoplysninger.
3. Erstat værdien af `$searchterm` med navnet, eller en del af navnet, på en hemmelighed, De har adgang til.
4. Kør scriptet fra den arbejdsstation, hvor Remote Desktop Manager er installeret.

```powershell
$url = 'https://mysecretserver/SecretServer'
$username = 'myusername'
$password = 'mypassword'
$domain = 'mydomain'   # leave blank for local users

$searchterm = 'VPN'

# Request an OAuth2 token with the username and password.
$loginName = if ($domain) { "$domain\$username" } else { $username }
$body = @{
    username   = $loginName
    password   = $password
    grant_type = 'password'
}

try {
    $token = (Invoke-RestMethod -Method Post -Uri "$url/oauth2/token" -Body $body -ContentType 'application/x-www-form-urlencoded').access_token
}
catch {
    Write-Host 'Authentication failed:' $_.Exception.Message
    exit
}

# Search secrets with the search term, authenticating with the token.
Write-Host 'Searching for:' $searchterm
$headers = @{ Authorization = "Bearer $token" }
$query = 'filter.searchText=' + [uri]::EscapeDataString($searchterm)

try {
    $result = Invoke-RestMethod -Method Get -Uri "$url/api/v1/secrets?$query" -Headers $headers
    Write-Host 'Got search results:' $result.records.Count
    $result.records | ForEach-Object { Write-Host 'SecretId:' $_.id '  Name:' $_.name '  FolderId:' $_.folderId }
}
catch {
    Write-Host 'Search failed:' $_.Exception.Message
}
```

Hvis scriptet godkender og returnerer Deres hemmeligheder, kan arbejdsstationen nå Secret Server, og problemet ligger i konfigurationen af posten i Remote Desktop Manager. Hvis scriptet mislykkes, peger fejlmeddelelsen på det netværks-, certifikat- eller kontoproblem, der skal løses på Secret Server-siden.

{% hint style="info" %}
Hvis Deres Secret Server-konto kræver tofaktorgodkendelse, mislykkes tokenanmodningen, medmindre De tilføjer engangskoden i en `OTP`-header, sådan som Remote Desktop Manager gør.
{% endhint %}

### Se også

* [Indstillinger for posten Delinea Secret Server](/rdm/da/knowledge-base/knowledge-base-articles/delinea-secret-server-entry-settings.md)


---

# 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/da/knowledge-base/troubleshooting-articles/test-secret-server-access-with-a-powershell-script.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.