oidc-op
oidc-op copied to clipboard
IdentityPython
An implementation of an OIDC Provider (OP)
The Fastapi example fails to start due to several issues: - Broken AuthorizationRequest import in utils.py - App ends prematurely without logging error due to initialization code in `startup` event...
`server.py -d` incorrectly references the Flask app rather than the container `oidc_provider`
We need to enumerate what extensions (RFC, I-D or OIDF spec based) that we have in the code base and how they can be used.
flask_op example fails to start because `oidcop.configure` does not have `Configuration` class anymore.
So, we are in the process of adding Token Exchange support on oidc-op as described in [RFC-8693](https://datatracker.ietf.org/doc/html/rfc8693) and we need feedback regarding the implementation. More specifically, we consider the following...
https://docs.python.org/3/library/enum.html that would prevent the creations of deprecated or unusable configuration fields
https://github.com/IdentityPython/oidc-op/pull/155/files#diff-fdd667e49ac1308c4888bce310067fbe8ffeee845186585dea4533179bca562fL228 we also need a timeslack paramenter (an integer in seconds) in the general configuration of an entity to have a more relaxed validation of exp
https://github.com/IdentityPython/oidc-op/blob/684355981ea12516e1b5ef3ed72a4ecf572109bf/src/oidcop/configure.py#L250 I have no `claims_interface` in my configuration but the logs say: ``` claims_interface not seems to be a valid configuration parameter ``` I guess it is an internal variable...
https://www.rfc-editor.org/rfc/rfc9126.html here https://github.com/IdentityPython/oidc-op/blob/master/docs/source/index.rst and also an usage example would be appreciated!
https://openid.net/specs/openid-connect-claims-aggregation-1_0.html this may introduce VC in oidcmsg? @rohe Probably we should have a separate library to handle VC and VP if you agree