Is it possible to store additional information in the userinfo response that ISN'T in the id_token

[johnlister]

We have a requirement to return more detailed (optional) information about a user in the userinfo request that isn't included in the id_token - in this case it is a list of valid roles/positions which can be very large. Most RPs only require the information in the id_token, but may call userinfo to get the complete "record" for a user. As it stands it looks like the data is identical (the session.id_token data is used in userinfo)

[aeneasr]

This is currently not possible! But you can of course override the userinfo endpoint and implement your own