Comment: Server (api/authentication/server.md)

[TitoVince35]

Comment/Problem

Is it to possible to ensure the client is authenticated somewhere else with JWT, without having a local authentication service?

It seems that from the moment you are using authentication module you MUST have an authentication service entity + route. In my case I have multiple Feathers / Express microservices. They all share a sercret to generate and/or check a JWT that is delivered by a single dedicated server app.

I managed to work this around pointing this route to my healthcheck service, but then it made my healthcheck service fail. So I had create a dummy-auth service/route, with all methods disallowed externaly. I feel this is wrong... What would be best?