> 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/embedded-credentials-not-working-in-chromium-based-browsers.md).

# Integrerede legitimationsoplysninger virker ikke i Chromium-baserede browsere

Løs, at integrerede legitimationsoplysninger ikke længere virker i Chromium-baserede browsere, ved at konfigurere en indtastningsmakro, der udfylder brugernavne og adgangskoder automatisk.

Google Chrome og dermed alle Chromium-baserede webbrowsere understøtter ikke længere integrerede legitimationsoplysninger i URL'er. Derfor kan legitimationsoplysninger ikke længere sendes direkte til en prompt om basisgodkendelse.

### Løsning

I Remote Desktop Manager kan der konfigureres en indtastningsmakro, som automatisk indtaster brugernavne og adgangskoder:

1. Vælg den post, der skal redigeres, og gå derefter til ***Egenskaber*** – ***Forbindelse*** – ***Hændelser***.
2. På fanen ***Efter åbning*** skal De sætte den indledende ventetid til 2 eller 3 sekunder og angive følgende i feltet til indtastningsmakroen: `$USERNAME${TAB}$PASSWORD${ENTER}`
3. Gå til ***Egenskaber*** – ***Sikkerhed*** – ***Sikkerhedsindstillinger***, og sørg for, at afkrydsningsfeltet ***Tillad adgangskode i variabel*** er markeret.

Med denne metode bør brugernavne og adgangskoder blive indtastet automatisk, når sessionen startes.


---

# 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/embedded-credentials-not-working-in-chromium-based-browsers.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.
