The Client Credentials Flow in OAuth2 is designed for non-interactive applications, such as automated processes or microservices, where the client is authenticated using its client ID and client secret. In this flow, the application sends a POST request to the authorization server, including its credentials and a request for an access token. If the credentials are verified, the authorization server returns an access token to the application, which can then use it to access its own account ([source](https://www.ory.sh/docs/oauth2-oidc/overview/oauth2-concepts#getting-a-client-token)). However, the Client Credentials Flow does not involve an end user, and it is typically used for server-to-server interactions. OpenID Connect (OIDC), on the other hand, is an identity layer on top of the OAuth2 protocol, which allows clients to verify the identity of the end user based on the authentication performed by an authorization server ([source](https://www.ory.sh/docs/getting-started/ory-network-oauth2)). Therefore, while you can use OAuth2's Client Credentials Flow with Ory, it does not directly involve OIDC because OIDC is about user authentication, and the Client Credentials Flow does not involve a user.