Project is deprecated, but does not name a replacement.

[DHowett]

This project is still one of the premier results for searches regarding Extensions and OAuth2, but it appears to be deprecated. Is there a successor?

[borismus]

It's deprecated in favor of chrome.identity API. On Mon, Aug 8, 2016 at 9:06 AM Dustin L. Howett [email protected] wrote:

This project is still one of the premier results for searches regarding Extensions and OAuth2, but it appears to be deprecated. Is there a successor?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/borismus/oauth2-extensions/issues/51, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQ8gBu0-z-FA6t55YQOQnGEFOMLKcl5ks5qd1NggaJpZM4JfM2P .

[DHowett]

Wait, seriously? That's the best news.

I've long thought extension development was a minefield, since it's pretty hard to find best practices.

Thanks!

[talent-io]

Sorry to bump this 2 years later, but it seems that this library cannot be completely replaced by the identity API: When using your own OAuth server, the identity API does NOT do any caching, you have to use the launchWebAuthFlow and this method does not do any caching (it contacts the auth server each time instead of storing the access token with it's expiration time in the browser and requesting a new access token when needed).

I've opened a question on Stackoverflow regarding this, if you have any information on the matter, I would love to hear about it.

[kingdonb]

I don't know anything about cacheing but managed to implement a bitbucket adapter and integrate it into my fledgling Chrome extension last night before I actually looked at the first line in the README.

Found the deprecation notice this morning, but I'm afraid the documentation and scaffolding around the Chrome.identity API was not as obvious or straightforward to me as this was. You mentioned that different OAuth2 providers are implemented differently, well your adapter pattern encapsulated that nicely for me, so nicely that I was able to go from "never wrote a Chrome extension in my life" to "built my own adapter for custom OAuth2 provider that wasn't on the list" in a night

To be fair, it was basically identical to the feedly adapter, but with new URLs from the bitbucket documentation. I'm just not sure how I find that out without your library of adapters.

(I'd like to contribute the Bitbucket adapter back via PR too, so someone smarter can tell me what else I'm doing wrong... but for now, it's working and that was honestly quite difficult, but probably easier than it should have been!)