During the OIDC login flow, the file `backend/modules/auth/providers/auth oidc provider.py` decodes the `id token` returned by the identity provider using `jose.jwt.get unverified claims()` instead of `jwt.decode()`. This process bypasses signature verification, audience (`aud`) validation, issuer (`iss`) validation, and expiry (`exp`) checking. Consequently, the extracted claims such as `email`, `sub`, or `preferred username` are used directly as the `user id` for the session.