exq VS guardian

Oban, backed by PostgreSQL or SQLite, also provides a queue-based job processing system. Exq, on the other hand, is backed by Redis. It provides features similar to Flume, but without built-in rate limiting and batch processing capabilities.

Enter Oban, which leverages Postgres' notify/listen functionality to provide a durable queue. Oban is solid and doesn't require Redis, which is cool. I end up using this in most projects I work on. If you absolutely need the speed of Redis, Exq is a pretty good option.

Job processing libraries compatible with Sidekiq, for example exq, won't deserialise your Dry::Struct arguments. This is most likely an acceptable tradeoff.

As for the original question, OP you should check out https://github.com/ueberauth/guardian if you want to roll your own auth. If not rolling you own you can just use a standard Oauth provider and validate their tokens (surprise they are JWTs) in you backend using their public keys.

AuthN: For authentication, I'd look at the built-in auth generator. If you need to add JWT things, joken and/or guardian can probably meet your needs.