When sending a sign-in request in the context of OpenID Connect, according to this source, it typically involves requesting an id_token (using "id_token" as the response_type
). Conversely, in the case of the auth code flow, as explained in this resource, the expected response_type
is usually "code". However, based on insights from this tutorial, it's worth noting that the response_type
can also be "code id_token" for the auth code flow.
https://i.sstatic.net/uZH91.png
It's interesting to observe that OpenID Connect can also be accomplished within the auth code flow scenario.
If you are considering using passport-azure-ad, here's a helpful method (designed for auth code flow) that could guide you through the process.
https://i.sstatic.net/HxuXc.png
The parameters (params
) mentioned refer to key elements extracted from the request or metadata, such as id_token, code, policy, metadata, cacheKey, and more.
The configuration items within oauthConfig
pertain to essential components for the OAuth flow (such as redirection, code redemption), including token_endpoint, userinfo_endpoint, etc.
Lastly, the optionsToValidate
include elements crucial for validating the id_token, which may consist of details like issuer, audience, among others.
Wishing you success with your implementation~