(requested on behalf of a customer)

The use case I wanted to highlight with Pact was to verify the JWT OAuth token structure in the header. We have already dealt with mocking credentials/bypassing credentials in a previous company but the issue we faced here are that the contents of the token kept changing (weird yes, but hence wanting to use this tool to show the value).

I wanted to make sure that the JWT token contents itself were validated via Pact. If that is not “reasonable” fine, but I was hoping there was an example of header decoding and verification. Specifics are that JWT is base64 encoded, the structure and contents of the token are mappable and verifiable, and we want to make sure the header contents when decoded are correct or when they do change it fails. Theoretically the token contents shouldn’t change frequently, but we’ve had it change enough times that it barely made it in as something I’d like to test with Pact and enforce via the contracts.