OAuth Refresh Token Flow: Is there a standard solution available?

[richardtop]

Hi, I'm using Get with CreateAPI and so far the solution is working great. I've actually been using a proprietary client based on your 2017y article earlier and implemented a custom OAuth token refresh flow.

In your 2022y article, you outlined another approach to use the Get Client Delegate to execute the refresh procedure:
https://kean.blog/post/new-api-client

I'm curious whether that's still the preferred approach to use with the Get client or whether there is an off-the-shelf solution, similar to https://github.com/OAuthSwift/OAuthSwiftAlamofire to be used.

If the method in the article is the preferred one, I think it would be good to incorporate it back into the Get documentation, so that it would be accessible from within this package.

This issue is an important one, as I think, OAuth is one of the most popular authentication methods out there and this library is likely to be used with it.

[kean]

I'm curious whether that's still the preferred approach to use with the Get client or whether there is an off-the-shelf solution

I'm not aware of any, but, in my experience, no server has been exactly the same and I always had to use a ad-hoc solution and a framework that accommodates it.

I think it would be good to incorporate it back into the Get documentation

That's a great suggestion, but, full disclosure, I'm not actively working on this project at the moment. I would be happy to review and merge changes suggested by others.

[richardtop]

Clear, then might add some docs, or even copy-paste them from your article, as I'm using it to build the client I need. Since there is another OpenAPI generator project, that pretty much works in pair with Get, that would be a great idea to have a sample for the OAuth retrier.

The ad-hoc solution in my case is just overriding a few methods in the delegate, as in your article.