-
-
Notifications
You must be signed in to change notification settings - Fork 493
Add reqval.fill_id_token
with technicals OIDC fields into id_token
#660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
A new RequestValidator `fill_id_token` has been introduced to replace `get_id_token`. It aims to have the bare minimum amount of fields to complete a full OIDC id_token support. `get_id_token` is still valid but optional, and if it is implemented, `fill_id_token` will not be called. The current `fill_id_token` came with full support of `aud`, `iat`, `nonce`, `at_hash` and `c_hash`. More could come in the future e.g. `auth_time`, ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments, but need to give it a better read still...
The only concern is when we need support claim extension if will be easy to do in configurable way. Any ideia on that? |
Rename hash_id_token into id_token_hash
Hi @skion, your initial comments have been solved. I have also added the missing unittests to increase coverage. Could you have another look? Hi @wiliamsouza, yes, claims is the next feature that it should be improved. I don't see any roadblocks to this.? |
reqval.fill_id_token
with technicals OIDC fields into id_token
reqval.fill_id_token
with technicals OIDC fields into id_token
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I quite like it, nice.
This function should always have a good client_id and redirect_uri, because it is called after validate_token_request()
Add support of:
Deprecate the 3.0.0
get_id_token
in favor offinalize_id_token
. However,fill_id_token
get_id_token
is still working if implemented. It gives the user the choice to either implement the full JWT build, or take the advantage of oauthlib and completing the id_token & signing it.Work is still to be done regarding
max_time/auth_time
,claims
, and maybe few others.