> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/authentication-external_users.md).

# authentication.external\_users

## Description

With this part you can get the authentication details for a stored external account, which you can use to authenticate the client when using a remote web API. You can create remote accounts using the AccessManagement portal or command-line script. For each remote account the system stores the purpose of the account - the scope of usage and which packages can retrieve the account information - the target server URL, the username/client id, and the password or RSA private key.

## Editor Fields

You configure this part with the following editor fields:

| Tab   | Field Name          | Description/Use                                                                                                                                                                                                                                                                                                                       | Type           | Optional/Mandatory |
| ----- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------ |
| Basic | Mode                | <p><strong>Get Authorization Header:</strong> This returns the authorization header, e.g. 'Basic dXNlcm5hbWU6cGFzc3dvcmQ' or 'Bearer ' for the given purpose and target server.<br><strong>List Accounts:</strong> This option returns a list of target servers for which an external account exists, based on the given purpose.</p> | Dropdown       | Mandatory          |
| Basic | Target Instance URL | If you selected *Get Authorization Header* this is the URL for the target instance.                                                                                                                                                                                                                                                   | String         | Mandatory          |
| Basic | Purpose             | This is the purpose for which the system uses the remote account. Listed purposes are based on the licenses installed.                                                                                                                                                                                                                | (options-list) | Mandatory          |
| Basic | Result              | This is the path in the context where the system stores the result of the processing.                                                                                                                                                                                                                                                 | Object         | Mandatory          |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/authentication-external_users.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.