devopsfaith/krakend-jose: jwk.go; 3 LoC

Found a possible issue in [devopsfaith/krakend-jose](https://www.github.com/devopsfaith/krakend-jose) at [jwk.go](https://github.com/devopsfaith/krakend-jose/blob/e9123d61e48151f5648e17412bb4745b4ecf9c50/jwk.go#L107-L109)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to k is reassigned at line 108

[Click here to see the code in its original context.](https://github.com/devopsfaith/krakend-jose/blob/e9123d61e48151f5648e17412bb4745b4ecf9c50/jwk.go#L107-L109)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, k := range keys.Keys {
keyMap[k.KeyID] = &k
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: e9123d61e48151f5648e17412bb4745b4ecf9c50

Start with jwk.go at lines 107-109 and inspect the surrounding key-processing code. Check whether the reported reassignment affects the references stored in keyMap, then look for existing tests covering JWK key mapping. Done means the reported analyzer finding is addressed or confirmed as intentional, with relevant tests passing.

Written by the indexing model from the issue text.