You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be beneficial to support multiple Resource Servers to identify one user. In the current setup the providers would either override each others entry, or create entirely different users for each individual provider. The solution would be to not store the identifier on the user record itself, but on an intermediary table.
This would take some rework, but if this sounds like something the extension should have, I'd happily tackle that
The text was updated successfully, but these errors were encountered:
It might be beneficial to support multiple Resource Servers to identify one user. In the current setup the providers would either override each others entry, or create entirely different users for each individual provider. The solution would be to not store the identifier on the user record itself, but on an intermediary table.
This would take some rework, but if this sounds like something the extension should have, I'd happily tackle that
The text was updated successfully, but these errors were encountered: