Marco Dinis f186fb451f Prevent creation of invalid App for AWS OIDC Integration (#51287) ...

* Prevent creation of invalid App for AWS OIDC Integration

When enabling AWS Access using an integration, the final address will be
a concatenation of the integration name and the proxy's public address.

The proxy must present a certificate valid for that address.
However, when the integration name has a dot, it will usually not work
with the proxy's certificate.
We know it won't work for Teleport Cloud, where the certificates only
allow for `<app>.<tenant>.teleport.sh`.

So, for Teleport Cloud enabling AWS Access is not possible.
For self-hosted, a warning is emitted.

* prevent new aws oidc integrations with invalid DNS labels

* add integration name to error message

* improve readability of validation.IsDNS1035Label call

2025-02-07 08:16:19 +00:00

..

integration_test.go

Prevent creation of invalid App for AWS OIDC Integration (#51287)

2025-02-07 08:16:19 +00:00