[#25] - include client allowed audiences in user access token#26

Merged

https-richardy merged 9 commits into

fix/25-include-client-allowed-audiences-in-user-access-token

Apr 25, 2026

Commits on Apr 25, 2026

fix(#25): include client allowed audiences in user access token generation
https-richardy
committed
fix(#25): this commit introduces overload for "generate access token async" to include audiences parameter
https-richardy
committed
fix(#25): this commit introduces validation for client identifier in authorization code grant type
https-richardy
committed
fix(#25): include missing domain concepts in usings.cs
https-richardy
committed
fix(#25): include client ID in metadata for access token generation
https-richardy
committed
fix(#25): this commit updates method to include audiences parameter for improved token generation
https-richardy
committed
fix(#25): this commit introduces audience assignment for client and validate in access token
https-richardy
committed
fix(#25): this commit introduces test for user access token generation with specified audiences
https-richardy
committed
docs(#25): this commit updates CHANGELOG for 4.2.1 release and README to reflect new version
https-richardy
committed