Fix or remove Audience Claim from standard claims about jwt

[kataras]

@geordee I decided to modify the Audience []string to a custom type of Audience Audience which it is still a []string so we have no breaking changes on Sign and Verify methods and how the standard "aud" claims is stored.

The issue is fixed by implemting the json unmarshal interface on that Audience new type (its code is identical to my previous comment).

[kataras]

Hello @geordee, you are right, there is no need to skip this claim though, you can use your own structure for standard claims too. We have two solutions for that:

1

On the claims.go:

	Audience []string `json:"-"`
	// RawAudience is used for encoding and decoding the Audience field, it can be a string or a []string.
	RawAudience json.RawMessage `json:"aud,omitempty"`

On the claims.go#ApplyClaims:

// ...

	if v := c.Audience; len(v) > 0 {
		dest.Audience = v
		dest.RawAudience, _ = json.Marshal(v) // lint: ignore
	}

On the verify.go#VerifyEncrypted:

		if aud := standardClaims.RawAudience; len(aud) > 0 {
			switch aud[0] {
			case '"': // it's a single string.
				var audString string
				err = json.Unmarshal(aud, &audString)
				if err == nil {
					standardClaims.Audience = []string{audString}
				}
			case '[': // it's an array of strings.
				err = json.Unmarshal(aud, &standardClaims.Audience)
			}
		}

This fixes the decoding issue you described above. However, on Sign mehods the value will be produced will be always a json array of strings, we can fix it by checking if the Audience == 1 and put the RawAudience to a single string (on the ApplyClaims method) but I think it is cleaner if we just keep it as []string always and let the decisions on the decode side as we did on 1.

2

If you want to explictly produce a single or a []string we must change the Audience type to a custom type or interface{} but it doesn't look right to me... waiting for your opinion.