> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/security/security-en/device/zugriff-und-authentifizierung.md).

# Access and Authentication

## Web interface

Login is performed using a device password. The password is verified with **PBKDF2-HMAC-SHA-512**, a random salt, and 100,000 iterations and stored non-reversibly.

{% hint style="info" %}
Assign a unique, sufficiently long password for each device and do not share it between systems.
{% endhint %}

## API keys

External systems and in-house tools access the API via API keys instead of the device password.

* Permissions can be restricted by HTTP method and path.
* Each key can be revoked individually.

Assign a separate key for each system with the minimum required permissions. This avoids passwords in scripts and configuration files.

## Access services

The accessible services can be enabled or disabled individually in the web interface:

| Service   | Description                              |
| --------- | ---------------------------------------- |
| **HTTP**  | Unencrypted web interface                |
| **HTTPS** | Encrypted web interface, must be enabled |
| **SSH**   | Administrative service access            |

{% hint style="warning" %}
Disable access services that are not needed. In particular, check whether SSH service access is required during operation, and if not, turn it off.
{% endhint %}

## Password recovery

If the device password is no longer known, it can be reset via powerIO Orbit. The device outputs an encrypted block that only powerIO Orbit or powerIO Support can decrypt.

{% stepper %}
{% step %}

### Request recovery on the device

On the device's login page **Reset Password** select. The device generates an encrypted block with an unlock code as well as hardware and serial number.
{% endstep %}

{% step %}

### Generate unlock code in powerIO Orbit

Open device management in powerIO Orbit and start the reset of the device password. Paste in the block; Orbit decrypts it and displays the matching unlock code.
{% endstep %}

{% step %}

### Reset password

Enter the unlock code on the device's login page. A new password can then be set.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Without access to powerIO Orbit, powerIO Support handles decrypting the block. Alternatively, support can issue a time-limited one-time password based on the serial number, which is valid for one hour and is not stored permanently.
{% endhint %}

## Device identity and powerIO Orbit

Optionally, a device can be connected with **powerIO Orbit** connected. This integration is disabled by default and is activated when needed.

<details>

<summary>Cryptographic classification</summary>

Device certificates and Orbit requests use **ECDSA with SHA-256** on the curve `prime256v1`. The subscription for a private channel is authenticated with **HMAC-SHA-256** authenticated. Transmission to powerIO Orbit is encrypted.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.powerio.com/hub/security/security-en/device/zugriff-und-authentifizierung.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.