Skip to content

Resource indicators audience policy - #123

Draft
lionick wants to merge 17 commits into
IdentityPython:mainfrom
lionick:resource-indicators-audience-policy
Draft

lionick wants to merge 17 commits into
IdentityPython:mainfrom
lionick:resource-indicators-audience-policy

Conversation

@lionick

@lionick lionick commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@c00kiemon5ter

Copy link
Copy Markdown
Member

The CI is failing due to missing or moved vars from the cryptography package.
We should check the changes introduced by version 47 and align with cryptojwt.

@c00kiemon5ter

c00kiemon5ter commented Sep 17, 2026

Copy link
Copy Markdown
Member

The issue comes from the combination of the cryptojwt and cryptography versions installed.
cryptography has removed support for certain curves. See the changelog for v47.0.0

https://cryptography.io/en/latest/changelog/#v47-0-0

BACKWARDS INCOMPATIBLE: Support for binary elliptic curves (SECT* classes) has been removed. These curves are rarely used and have additional security considerations that make them undesirable.

and the fix that is included in the latest (v1.11.0) cryptojwt version:

https://github.com/IdentityPython/JWTConnect-Python-CryptoJWT/pull/194/changes

@lionick

lionick commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

However, v1.11.0 declares requires-python: >=3.10 — there's no released cryptojwt version that has this fix and still supports 3.8/3.9 (v1.10.0, the last one that does, predates the fix).

So picking up the fix means bumping to cryptojwt>=1.11.0 and dropping Python 3.8/3.9 from this repo's CI matrix — which lines up with both already being past their own upstream EOL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants