OIDC SSO move to JWT claims from userinfo attributes

Feature Requests
1

The idea is:

Allow for modifying the SSO flow, such that n8n utilizes JWT claims instead of interrogating the userinfo endpoint. After having the jwt token, there’s not necessarily a need to make another web call to get user information: all of it can be provided within the jwt token itself.

My use case:

In addition to simplifying the login flow and eliminating a http request, this also allows for substituting values where there might not have been one. For instance, if I had an account that didn’t have a mailbox configured, I could modify the jwt claim so that it sends the email claim with another value. Even better would be to allow mapping of n8n properties (username, email, name, etc) to jwt claims directly. I’d use username → upn, for instance.

I think it would be beneficial to add this because:

This simplifies the login flow and allows for greater flexibility on the part of the n8n admins

Any resources to support this?

Are you willing to work on this?

I’m pleased to test and give feedback. I’m not a developer.

2

Hey @lanedsmu,

Don’t forget to add a vote to your request to make it count, Can you provide a bit more information on what you would like to do?

You mentioned SSO but also an HTTP Request so is this more for webhook authentication in a workflow to then map to a users credential or something else?

1 Like