Max Truxa
Max Truxa
I work around this by setting `certbot_auto_renew: false` on Debian, but it sure would be nice to have this behavior by default.
Still relevant.
Fixed by #425.
Provided you're talking about v3 and not v2 (the version published on npm): You should be able to access the `client` and `user` objects through the result from `OAuth2Server#authenticate`: ```...
This should really be documented somewhere. @ruimarinho: Could you add this to whichever v3 milestone you're targeting for documentation?
This is now documented [here](https://oauth2-server.readthedocs.io/en/latest/api/oauth2-server.html#authenticate-request-response-options-callback).
I think the use case that the default handler covers is one of the rarer ones, as most OAuth2 servers probably implement user authentication using an existing (session-based) login mechanism....
@knightcode If you don't have a user at that point something else is wrong and there is no sane way to recover from this condition. @mjsalinger @lfk @nunofgs: I'm going...
@Doom100500 Make sure you are using the correct name for the npm package. There were one or two "alternative" names which are *not* updated (anymore?). [`oauth2-server`](https://www.npmjs.com/package/oauth2-server) is the right one....
@oauthjs Could anyone with write access mark the npm package `node-oauth2-server` as deprecated?