OpenID Connect, or OIDC, is an identity standard built on OAuth that lets one system verify who a user or workload is. An identity provider issues a signed token that states who the subject is, and another system can check the token instead of holding its own password or key.
It matters because it is the basis of many sign-in systems and of workload identity. For example, a build pipeline can present a short-lived signed token to a cloud provider, which checks it and grants temporary access, so no long-lived key needs to be stored.
It is a standard, and how it is used is up to each system. The access that results depends on how trust is configured: if the rules about which tokens are accepted are too broad, tokens from unintended sources could be allowed. Setup differs between providers, and mistakes in it are a real source of problems.
When using it, restrict which issuers and subjects you accept as narrowly as you can, keep token lifetimes short and test that tokens from other sources are refused.