Jörn Friedrich Dreyer

autodecode base64 encoded uuid userid

2

Keycloak base64 encodes the AD binary objectGUID. We can automatically detect that. No need for a new env var.

We now expect the `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_CA_CERT` env var to be a path to a certificate in pem format, rather than a `byte[]` (which won't work with env vars).

OC_REVA_GATEWAY_TLS_MODE and OC_REVA_GATEWAY_TLS_CACERT are not used anywhere in the codebase. The actual env vars for configuring the grpc client tls mode have been OC_GRPC_CLIENT_TLS_MODE and OC_GRPC_CLIENT_TLS_CACERT all along

apply the same endianness handling as in https://github.com/opencloud-eu/reva/pull/431

## Describe the bug Whenever we start the settings service it writes the configured role bundles to the system storage: ```go // we need to lazy initialize the MetadataClient because...

bump pkg/tracing semconf to 1.37.0

1

this is the only place where we use this old version

"go.opentelemetry.io/otel/exporters/jaeger" is deprecated

1

OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp] or [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc] instead.

When debugging, the username attribute was configured incorrectly and the username was always empty. This will help in error cases.

proposal to fix https://github.com/opencloud-eu/opencloud/issues/1906 We can rely on the otlp SDK to parse and configure the traces provider. The only env var we need to handle is `OTEL_TRACES_EXPORTER` to decide...