Open cloudhary opened 5 years ago
You may now proceed to plug in your real user/account model, expand the views with password resets, registrations, social signup, as long as your routes are in the same namespace you have access to the original authentication request parameters and interaction details, those are referenced by a path specific cookie and stored using your backend adapter. oidc-provider expects that you resolve all interactions in this one go, if you fail or purposefully omit one the resumed authentication will fail with a corresponding error.
Done on the frontend by OG singpass so not that important?
You want an account with us. How should we go about doing that?