Could not create indirect identity provider vCenter

[chrispro-21]

Describe the bug
When following documentation from Authentik Docs I get the following error from vCenter when trying to add the Okta SSO provider

To Reproduce
Steps to reproduce the behavior:

1. Follow steps to configure Authentik
2. Follow steps to configure vCenter until step 6 ("Click Next, and then Finish.")
3. Click Next, and then Finish.
4. See error: "Could not create indirect identity provider" from vCenter

Expected behavior
The new provider is added to vCenter and would show up in the providers section.

Screenshots

Logs

Authentik logs when hitting "Finish" in vCenter

server-1          | {"auth_via": "secret_key", "domain_url": "0.0.0.0", "event": "/api/v3/crypto/certificatekeypairs/cb13272f-e8ac-4b24-bced-a7db7b91892e/", "host": "0.0.0.0:9000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 90440, "remote": "127.0.0.1", "request_id": "1a7d0fc68bd04b7590ef265bbfd0b668", "runtime": 106, "schema_name": "public", "scheme": "http", "status": 200, "timestamp": "2025-01-04T04:59:22.899282", "user": "ak-outpost-03336f82eb3c459e8dc6c075f2dbd80f", "user_agent": "goauthentik.io/outpost/2024.12.1"}
server-1          | 2025/01/04 04:59:22 http: TLS handshake error from VCENTER_IP_ADDRESS:51702: remote error: tls: unknown certificate
server-1          | {"auth_via": "secret_key", "domain_url": "0.0.0.0", "event": "/api/v3/outposts/instances/", "host": "0.0.0.0:9000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 90440, "remote": "127.0.0.1", "request_id": "abdd3731ec14425f8f61f29473dae464", "runtime": 129, "schema_name": "public", "scheme": "http", "status": 200, "timestamp": "2025-01-04T04:59:24.989953", "user": "ak-outpost-03336f82eb3c459e8dc6c075f2dbd80f", "user_agent": "goauthentik.io/outpost/2024.12.1"}
server-1          | {"auth_via": "secret_key", "domain_url": "0.0.0.0", "event": "/api/v3/outposts/proxy/?page=1&page_size=100", "host": "0.0.0.0:9000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 90440, "remote": "127.0.0.1", "request_id": "2f107cca5f52406f9cdc541528335ac7", "runtime": 109, "schema_name": "public", "scheme": "http", "status": 200, "timestamp": "2025-01-04T04:59:25.149976", "user": "ak-outpost-03336f82eb3c459e8dc6c075f2dbd80f", "user_agent": "goauthentik.io/outpost/2024.12.1"}
server-1          | {"event":"updating brand certificates","level":"info","logger":"authentik.router.brand_tls","timestamp":"2025-01-04T04:59:25Z"}
server-1          | {"auth_via": "secret_key", "domain_url": "0.0.0.0", "event": "/api/v3/core/brands/?page=1&page_size=100", "host": "0.0.0.0:9000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 90440, "remote": "127.0.0.1", "request_id": "865def08a8954416ac2533485b0541a4", "runtime": 82, "schema_name": "public", "scheme": "http", "status": 200, "timestamp": "2025-01-04T04:59:25.285351", "user": "ak-outpost-03336f82eb3c459e8dc6c075f2dbd80f", "user_agent": "goauthentik.io/outpost/2024.12.1"}

vCenter log found in graylog:

2025-01-03T23:48:35.028-05:00 [tomcat-exec-30 [] INFO com.vmware.vcenter.trustmanagement.authbroker.BrokerClient opId=] API request CREATE_IDENTITY_PROVIDER to url http://localhost:1080/external-vecs/http1/vcsa.REDACTED.tld/443/federation/t/customer/broker/identity-providers returned unexpected response code 400 and the following error information: {"errors":[{"code":"oidc.config.api.validation.error","message":"Failed to retrieve OIDC endpoints from configuration url: https://sso.REDACTED.tld/application/o/vcsa/.well-known/openid-configuration.","parameters":{"configUrl":"https://sso.REDACTED.tld/application/o/vcsa/.well-known/openid-configuration"}}]}

Version and Deployment (please complete the following information):

• authentik version: 2024.12.1
• Deployment: docker-compose

Additional context

• I do run an internal CA (HashiCorp Vault) which has been added to both the Authentik docker host and the vCenter appliance
• I export logs from vCenter to graylog

Edit: fixed markdown formatting issue

[SFoster5841]

G'day Guys

Having the same issue here,

i have tested versions 2024.4 though to 2024.12 and all seem broken

Same logs are appearing both on vCenter and Authentik, i have ensured my Root/Sub CA Certs are added to the SSO Host and vCenter but nothing seems to work so far

Thanks
Saturn