> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/codeunit-referenz/72242963-soudhl-secret-mgt.md).

# 72242963 SOUDHL Secret Mgt

## Verantwortung

Kapselt Isolated Storage im `DataScope::Company` für DHL- und PDF-Konvertierungs-Credentials. Secret-Werte gehören nicht in Tabellen, Source, Telemetrie oder GitBook.

## Öffentliche Procedures

### Speicherung

* `SetSecret(KeyName: Text; SecretValue: Text)` – leerer Wert löscht den Key, sonst wird er gesetzt.
* `GetSecret(KeyName: Text) SecretValue: Text` – fehlender Key liefert leeren Text.
* `HasSecret(KeyName: Text): Boolean` – prüft Existenz.

### Kanonische Keynamen

* `ApiKeyName(): Text`
* `ApiSecretName(): Text`
* `AccountNumberName(): Text`
* `ParcelClientIdName(): Text`
* `ParcelClientSecretName(): Text`
* `AzureUrlName(): Text`
* `AzureKeyName(): Text`

Die Methoden verhindern, dass Keynamen an mehreren Stellen dupliziert werden. Die konkreten Secret-Werte sind niemals Bestandteil der Entwicklerdokumentation.

## Verwendung in der App

* Configuration Assisted speichert Express-Key, Secret, Account und Parcel-Overrides.
* API Management liest Express-, Parcel- und Konvertierungssecrets.
* Statusfelder `Account Set` und `Credentials Set` sind nur UI-Indikatoren; maßgeblich ist Isolated Storage.

## Sicherheitsvertrag

Die Codeunit ist technisch Public, aber kein allgemeiner Secret Store für Consumer-Apps. Eine abhängige App soll:

* eigene Secrets unter eigenem Namensraum speichern,
* DHL-Keys nur nach ausdrücklicher fachlicher Vereinbarung verändern,
* niemals `GetSecret` ausführen, um Credentials zu loggen oder weiterzugeben,
* Einrichtung bevorzugt über den DHL-Assistenten durchführen lassen.

## Datenwirkung

Isolated Storage je Company; keine Business-Central-Tabelle und kein Commit.


---

# 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.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/codeunit-referenz/72242963-soudhl-secret-mgt.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.