Add function for silently refreshing refresh token about generic-oauth2 HOT 7 CLOSED

The Secure Storage Plugin should be used by users; they should store the tokens on their end. Using that plugin is just a recommendation (for securely storing the refresh tokens), in the end the users are free to do with the tokens whatever they want to do.

I just built a first version of the refresh functionality for Android and it seems to work 😄 please feel free to take a look at my PR and provide feedback!

from generic-oauth2.

@tomfebry Yes, we're using it in production now for iOS and Android. 😄 If you really need it now, you could consider using my NPM package (https://www.npmjs.com/package/@dennisameling/capacitor-oauth2) until my PR has been accepted into the main repository.

from generic-oauth2.

@dennisameling thx for the PR. I will release a new version next week.

from generic-oauth2.

I'm closing this issue for the upcoming release and created a new one for the feature regarding the PWA/Web part. Hope that's ok. See #65

from generic-oauth2.

I like the idea. Just one question.

The Secure Storage Plugin should be used by users of the plugin not the plugin itself? So it is sth we need to documentation?

I would really like to keep the plugin only depending on Capacitor Core + Core plugins. Alternatively I would rather implement the secure store feature myself. I doesn't seem to be that much work.

from generic-oauth2.

Just finished first working version of iOS refresh token functionality. First time working with Swift, so if something looks weird in the code, please comment and I'm happy to fix it 😄 Also provided some basic documentation on how to refresh a token from within the app.

from generic-oauth2.

I am trying to implement this into an ionic application, did you manage to get refresh tokens working?

from generic-oauth2.