Jared Hanson

You can specify any URL you want using `options.authorizationURL` and `options.tokenURL`. Is that not sufficient?

You should be able to put log statements here: https://github.com/jaredhanson/passport-oauth2/blob/master/lib/strategy.js#L402 to get at the original error. That should help identify and DNS or other related issues. Please post here any...

That'd be awesome. If you can provide a sample of this type of response (or a way to reproducible force it to happen), I'll add a test case for it....

It's not clear from the information provided that this issue is related to `passport`. Could you post a screenshot of the error or stack traces from the code?

When you say "this is the options sent to the request" ``` { authorizationURL: 'https://localhost:3000/login/oauth/authorize?state=%2Ftoken', scope: 'openid cloud_controller.write cloud_controller.read', response_type: 'code', redirect_uri: 'https://localhost:5000/auth/callback' } ``` How are you passing the...

`state` and `scope` should be documented. The rest are not documented simply because they are not generally useful, and I tend to favor explaining less options in order to reduce...

Have you identified whether the issue is this package, or the underlying node-oauth package? The underlying package is responsible for serializing credentials, so it may be there. Sent from my...

For those asking for this to be merged - can you please provide rationale? Why would you want a status code other than `302` when redirecting to an OAuth server?

Thanks @danielcorin. I realize there is flexibility in the spec, but I'm looking for actual functionality that requires a non-302 redirect, and thus a changes to the implementation in this...

There currently is not, no. I would be willing to accept a pull request that implemented this functionality. It would also required a corresponding pull request to the underlying [`oauth`](https://github.com/ciaranj/node-oauth)...