-
Notifications
You must be signed in to change notification settings - Fork 25
Version 2.1.0 #109
Version 2.1.0 #109
Conversation
acr value in claims parameter was not treated correctly.
Reflect version in pyproject.toml file.
Allowing specification of a client DB in the configuration file.
To fix token backward compatibility.
Userinfo claims
This takes care of that.
This takes care of that.
Clear txt sid
Great, do we have to label as BREAKING CHANGE the new cdb approach? Is there something to explain in the docs? |
do we have to say that load/dump/flush methods MUST be adopted and this approach could be breaking for the implementers? |
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.
overall the code looks pretty ginvolvedood, great job Roland
The new cdb approach isn't breaking anything. It allows new functionality that is what it does. |
It looks very good to me, thank you |
tested on django-oidc-op, all passes, very good |
Fixed a couple of backward compatibility issues. Like accepting old tokens and allowing configuration of a client database separate from the session database.
Also made sure that if an acr value was specified using the claims parameter in authorization request, it would be honoured and reported back in the ID Token or in the response from the user info endpoint.