There is no way to get back information from FA when it calls your connector endpoint. What I ended up doing was creating separate applications for each portal in our app. WHen FA calls my connector, now I can look at the incoming applicationid and know which portal this user belongs too and that solved my issue.

@dan Oh I see. The error in the response says:

"because it was missing a unique id in the [user.id] or enough information to store in FusionAuth (i.e. an email or username)"

In other words, "either Id or email" is missing from your request. Which makes boolean sense when thinking about it carefully.

But when first reading it, I though it meant "you need either Id or email", which is very different. I supplied one of those. I though that was what the "or" meant.

This error could be better as:

"because it was missing a unique id in the [user.id] or enough information to store in FusionAuth (i.e. an email or username). Both are necessary"

Internal Note: tracking via https://github.com/FusionAuth/fusionauth-issues/issues/1231

You can increase the timeout of the login request to a connector. If you sign in to the admin UI and navigate to "Settings" and then "Connectors", you can modify either of these settings:

"Connect timeout" "Read timeout"

The default value for these is 2 seconds.

There is more documentation on this topic here: https://fusionauth.io/docs/v1/tech/connectors/generic-connector/

You can also change them via the API, if that's more in line with your current workflow. That's documented here: https://fusionauth.io/docs/v1/tech/apis/connectors/generic/#update-the-generic-connector

@joshua That actually helps very much, thanks!