[vladimir-mencl-eresearch]

The lambda function passed to pyop handle_token_request as extra_id_token_claims does not support stateless mode, it relies on user attributes available in the database.

As pyop handle_token_request already supports getting extra_id_token_claims with authz_state.get_extra_id_token_claims_for_code, just pass {} (not the lambda function) and let pyop get the claims this way.

All Submissions:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what problem you are trying to solve with this PR?
• Have you added information on what your changes do and why you chose this as your solution?
• [N] Have you written new tests for your changes?
• [N] Does your submission pass tests?
• [N] This project follows PEP8 style guide. Have you run your code against the 'flake8' linter?

[vladimir-mencl-eresearch]

Hi @c00kiemon5ter ,

Thanks for the new work on cutting releases of pyop and SATOSA.

That has prompted me to try if I can use extra_id_token_claims in stateless mode now ... and while I was getting a KeyError in pyop/userinfo.py line 34, I found an easy fix.

Please let me know if OK to merge.

Cheers,
Vlad

[c00kiemon5ter]

Thanks!