Here's how it works:
- Your login page uses the BindID SDK to initiate an OIDC authorization request.
- BindID loads an OIDC IDP page which is used to authenticate the user.
- Once completed, BindID redirects to your redirect URI which now contains the authentication result.
- Your redirect page uses the BindID SDK to extract the authorization code, and then sends it to your backend so it can be exchanged for an ID token (see Get User Identity and Trust).