we are currently using the passport-openidconnect strategy for the authentication in node-red.
Because node-red wraps the verify-callback in another function when creating the strategy, which has an arity of 0, our verify-callback always gets called with only three arguments. As result we can neither have access to the user's profile nor to the tokens.
we are currently using the passport-openidconnect strategy for the authentication in node-red. Because node-red wraps the verify-callback in another function when creating the strategy, which has an arity of 0, our verify-callback always gets called with only three arguments. As result we can neither have access to the user's profile nor to the tokens.
Here is a link: https://github.com/node-red/node-red/blob/f1e7ec0c6bc33d4d0f6286012ef4d5aa817ac0b5/packages/node_modules/%40node-red/editor-api/lib/auth/index.js#L177-L196