Robust Generic Connector

[harishreddy-m]

A better generic connector

Problem

Control generic connector behaviour from different responses of API webhook configured in connector

Solution

The generic connector API webhook behaves in a bit red/green fashion. "User is imported and login succeeds" or not.
It would be better to improve the behaviour like:

When API webhook returns response with

• user.verified: false, user.active: false -> Block the login and redirect the user to respective flow/screens

Alternatives/workarounds

write a webhook that listened to the user.create event, check to see which connector had created the user, and then deactivate the account using the user API

[robotdan]

Thanks for the suggestion @harishreddy-m .

If I understand the issue, when the generic connector returns a response with user.verified: false or user.active: false FusionAuth optionally respond differently.

For example :

{
  "user": {
    "active": false
  }
}

On the "normal" Login API, if we see a user that is active: false this is a soft-deleted user, or "inactive" so we would return a 423. But I believe it is not currently working like that when using the generic connector.

We don't currently have any configuration for user.verified - this is always allowed and it is up to the caller to decide if this should limit the user's authority.

We have had requests in the past to add configuration for this state to optionally force validation. This is something we can look into.