Hi everyone, I don't know if it's a feature or a b...
# talk-oathkeeper
Hi everyone, I don't know if it's a feature or a bug. But if your access rules allow POST/GET/PUT, the HTTP method you use will be forwarded to the authenticator. This is a problem for me because I've setup a bearer token authenticator under the route
GET /api/1/users/jwt
which returns the
{subject: String, extra: {}}
as outlined in the docs But when I fire a POST request to
oathkeeper will make a call to
POST /api/1/users/jwt
to authenticate and my server will return 404. Is the expectation that we need to support all HTTP methods for the authentication URL or is there a way to override the HTTP method used to authorize the request?
Hi @square-addition-83225 Yes you are correct, this is a problem with Oathkeeper and has come up in the past - see this discussion https://github.com/ory/oathkeeper/discussions/697 Would you be up to create a PR for this?
@proud-plumber-24205 I'm not familiar with golang, but might be a good opportunity to learn it. Will give it a go
Thank you @square-addition-83225 😁❤️