BearerStrategy initialization is asynchronous

[kayjtea]

When initializing metadata from URL, initialization is asynchronous. This leads to the server listening for HTTP requests before passport is fully ready to be used. In a situation where instances are spun up as needed, this leads to some web requests failing. Initialization should probably take a done callback as well as an error callback. Or maybe initialization should be synchronous. Have any of you run into this problem?

[kayjtea]

Oops I see the callback is passed err === null on success.

[kayjtea]

But callback isn't exposed by Strategy initialization.

[lovemaths]

@kayjtea This is issue #90 , we already fixed this problem in dev branch and we will put the fix into the next release. Thanks.

[lovemaths]

Shipped the fix in the most recent release (v2.0.1), closing the issue.