"no connections enabled for the client" with OIDC enterprise domain connection

Hey there - I’ve promoted an enterprise OIDC connection to be a domain connection via the management API and I’m attempting to authenticate against it with a third party client, and I’m getting a “no connections enabled for the client” error. I’ve attempted this with a client that was promoted (demoted?) to third party via the management API, and with one I created via dynamic client registration, and I’m getting the same error. It’s my understanding that that domain connection should be available to all third party clients - am I missing something here?

1 Like