Fix issue with MapClaims VerifyAudience []string

[Waterdrips]

There was an issue in MapClaims's VerifyAudiance where a []string (which
is valid in the spec) would return true (claim is found, or nil) when required
was not set.
It now checks interface types correctly and has tests written

Fixes: #6
Signed-off-by: Alistair Hey alistair@heyal.co.uk

[Waterdrips]

This is validating against this part of the RFC https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.3

4.1.3.  "aud" (Audience) Claim

   The "aud" (audience) claim identifies the recipients that the JWT is
   intended for.  Each principal intended to process the JWT MUST
   identify itself with a value in the audience claim.  If the principal
   processing the claim does not identify itself with a value in the
   "aud" claim when this claim is present, then the JWT MUST be
   rejected.  In the general case, the "aud" value is an array of case-
   sensitive strings, each containing a StringOrURI value.  In the
   special case when the JWT has one audience, the "aud" value MAY be a
   single case-sensitive string containing a StringOrURI value.  The
   interpretation of audience values is generally application specific.
   Use of this claim is OPTIONAL.

[oxisto]

Ah perfect, a fix without touching the claims struct 👍

[Waterdrips]

Have we decided what go versions to support and if we are using github actions OR travis ?

[oxisto]

Have we decided what go versions to support and if we are using github actions OR travis ?

Basically I have enabled GH actions for those versions we want to support (>= 1.11). Travis has 1.7-1.10 currently. My idea is then to gradually remove versions from it (Travis), when PRs reasonably demand it, until Travis can be removed completely.

[oxisto]

LGTM

[lggomez]

LGTM