support additional/arbitrary JWK parameters
Issue #63
closed
Currently the JsonWebKey class hierarchy only deals with JWK parameters that it explicitly knows about. Custom or unknown parameters are discarded on parse or instantiation with the parameter map constructors. And there's no setters or anything to use if/when constructed with a key.
There should be some support for custom or unknown parameters. And maybe some hooks in SimpleJwkFilter too.
Comments (5)
-
reporter
-
reporter
- edited description
-
reporter
Actually, just going to make the changes to support for additional/arbitrary parameters in JsonWebKey, PublicJsonWebKey, EllipticCurveJsonWebKey, RsaJsonWebKey, and OctetSequenceJsonWebKey. Not going to take it further at this point to do anything with SimpleJwkFilter or selectors that use it.
-
reporter
- changed status to resolved
calling this done w/ just b1672dd
-
reporter
- changed status to closed
released with v0.5.1
- Log in to comment
b1672dd support for additional/arbitrary parameters in JWK as 1st part of Issue
#63