[#955] Using third party authentication providers (Azure B2C)

Migrated from Redmine #955 | Author: Daniel Waghorn
Status: New | Priority: Normal | Created: 2022-11-02


Hello,

We are currently in discussion with SimplyBook on behalf of a client whom we are developing an integration with. One of the use cases we are currently investigating is allowing an authenticated user to book via our own application which wraps the SimplyBook API via our own application API.

Currently our users are authenticated via Microsoft Azure B2C which authenticates our users in-application, and we get a JWT token as a result which we can use to call our APIs, authenticating and identifying the user. We are aware that SimplyBook offer an integration with B2C which would allow our users to sign in using their existing credentials, but we don’t want to have to present a login window to a user when they’ve already authenticated.

Would it be possible to provide something like our JWKS URL to SimplyBook to allow SimplyBook’s APIs to validate a caller to the API using the token we already have for the user? This would also identify users uniquely against the SimplyBook API.

Best Regards,
Daniel Waghorn

Redmine Admin wrote:

hi, unfortunately this is not possible