Update how to handle jwtMiddleware in martini

[barismar]

Description

FIx returning invalid response text/plain <invalid Value> instead of application/json { "text": "All good. You only get this message if you're authenticated"} when hit endpoint /secured/ping, how to fix this issue is by wrapping jwtMiddleware.CheckJWT with a function that requires params request and response that injected by Martini.

References

Include any links supporting this change such as a:

• Issue https://github.com/auth0/go-jwt-middleware/issues/17
• https://github.com/go-martini/martini#service-injection

Testing

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation for new/changed functionality in this PR or in auth0.com/docs
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not master

[JayHelton]

Hey there! Thanks for submitting a PR.

I believe the root cause of this issue found in the paragraph right above the one linked in the pr https://github.com/go-martini/martini#return-values :

If a handler returns something, Martini will write the result to the current http.ResponseWriter as a string

The JWT Middleware we provide here will return an error or nil. When you wrap it like you did in this PR, the handler doesnt return anything and doesnt write to the response.

@grounded042 This might be something to think about as we rework the internals.

Aside from that, I think this is a fine workaround, albeit It is not ideal to have to use the middleware like this.

[grounded042]

Yeah, this is definitely a bummer to have to use this workaround. Let's merge this in for now as it's great to have this, but in the future we should find a better way to handle this.