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

# Embedded credentials not working in Chromium-based browsers

Fix embedded credentials no longer working in Chromium-based browsers by configuring a typing macro to auto-fill usernames and passwords.

Google Chrome, and therefore every Chromium-based web browser, no longer support embedded credentials in URLs. As a result, credentials cannot be pushed directly into a basic authentication prompt anymore.

### Solution

In Remote Desktop Manager, a typing macro can be set up to automatically input usernames and passwords:

1. Select the entry to edit, then go to ***Properties*** – ***Connection*** – ***Events***.
2. In the ***After Open*** tab, set the initial wait time to 2 or 3 seconds, and enter in the typing macro box: `$USERNAME${TAB}$PASSWORD${ENTER}`
3. Go to ***Properties*** – ***Security*** – ***Security Settings***, and make sure the ***Allow Password in Variable*** checkbox is checked.

Using this method, usernames and passwords should be automatically typed on session launch.


---

# 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/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.