Some users have requested OAuth support instead of the bespoke JWT authentication system.
Poem should be able to handle this: they have an example using GitHub OAuth to do things. Some messing with this and OAuth2 should hopefully make it work.
The main problem, however, lies in the rest of the HTTP server, which assumes that the authorization passed contains the ID of the logged in user (see the auth.0.ids littered all over it). OAuth support would need some way of keeping this information in the passed token.
Some users have requested OAuth support instead of the bespoke JWT authentication system.
Poem should be able to handle this: they have an example using GitHub OAuth to do things. Some messing with this and OAuth2 should hopefully make it work.
The main problem, however, lies in the rest of the HTTP server, which assumes that the authorization passed contains the ID of the logged in user (see the
auth.0.ids littered all over it). OAuth support would need some way of keeping this information in the passed token.