OAuth and OpenID Connect (OIDC) allow third-party applications to access user accounts and private details from other websites and services, but implementing them securely can be complex. Nesting these protocols, where one OAuth/OIDC provider authenticates with another, introduces further risks that must be carefully managed through authorization controls and consent workflows. Overall system architecture and flows need attention to prevent unintended access to user data across multiple services.

1. Nested OAuth/OIDC (or social login) @spoon