KuvaszBLOCK

private const val PKCS8_HEADER = "-----BEGIN PRIVATE KEY-----"

private const val PKCS1_HEADER = "-----BEGIN RSA PRIVATE KEY-----"

private const val SEC1_HEADER = "-----BEGIN EC PRIVATE KEY-----"

gradle-wrapper.jar

apiKeyConfig = ApiKeyConfig().apply { apiKey = "some-non-blank-api-key" },

client-secret: 'ThisIsASecretThatIsLongEnoughToBeValidButItIsNotUnique'

client-secret: 'ThisIsASecretThatIsLongEnoughToBeValidButItIsNotUnique'

client-secret: 'ThisIsOnlyA35CharacterLongSecret123'

const val PASSWORD = "e2e-admin-password-123"

.also { Files.writeString(it, "-----BEGIN PRIVATE KEY-----\nMIIE\n") }

.also { Files.writeString(it, "-----BEGIN PRIVATE KEY-----\nnot really\n-----END PRIVATE KEY-----\n") }

.helmignore

val otherHostMockServerUrl = "http://127.0.0.1:1080"

val address = DockerDaemonUrl.parse("http://10.0.0.5", tls = null)

DockerDaemonUrl.parse("http://10.0.0.5", tls = tlsMaterial())

val address = DockerDaemonUrl.parse("https://10.0.0.5", tls = null)

val address = DockerDaemonUrl.parse("https://10.0.0.5:8443", tls = null)

- **Mutual TLS authenticates, but it doesn't authorize.** A valid client certificate gives **full access** to the daemon, so treat the client key as a root credential, and don't reuse it for anything 

By default **any user your OIDC provider successfully authenticates is allowed to sign in** and is granted full access. If your provider serves a broader audience than the people who should access _Ku

Without an email allowlist, **every user the OIDC provider can authenticate gets full access to _Kuvasz_** — including the REST API. If your provider is shared with other applications, backed by a pub

Docker hosts are **defined in your configuration file**, similarly to the [integrations](integrations.md), and every monitor refers to its host **by name**. They can't be created or modified on the UI

If it's set to `false`, the authentication will be completely disabled, and you can access the web UI or the API without any credentials.

4. To get your chat ID, send a message to your desired chat and then visit `https://api.telegram.org/bot<YourApiToken>/getUpdates` in your browser, where `<YourApiToken>` is the token you received fro

Once OIDC is enabled, the **Settings** page (and the `/settings` endpoint of the [REST API](../features/api.md)) shows the effective OIDC configuration — the issuer, client ID, the exact redirect (cal