Charlie Jonas

@avivek you may have moved on and don't care anymore, but I wanted to provide an update to this: > Would it be possible to not tie the solution to...

@wuservices I went ahead and added this code via a couple utility functions. You need to use `3.0.0-rc.22` (I'm about to release, so if you are starting a new project,...

@wuservices possibly... I can add the user-agent flow... It's basically JUST redirecting the user via the authorization and then access token is returned in the redirect url. Your client code...

👍 sounds like a good use. I will push a version today that should "support" the user-agent flow (it's really just updating a type). The API for this will likely...

@wuservices types for this should setup in `@3.0.0-rc.23`... I haven't actually tested, so LMK if it doesn't work. Docs are here: https://app.gitbook.com/@cjonas/s/ts-force/v/3.0/guides/connecting-with-salesforce/oauth/user-agent-flow Also added docs for the original issue: https://app.gitbook.com/@cjonas/s/ts-force/v/3.0/guides/connecting-with-salesforce/re-auth-on-token-expiration...

Ugh, ya I haven't tried it in the browser, but Salesforce CORS is a mess so that doesn't surprise me. Even with an interceptor, it's going to be a [tricky...

nice work! Maybe you could provide a quick example of how you are using it, so I can update [the docs](https://app.gitbook.com/@cjonas/s/ts-force/guides/connecting-with-salesforce/re-auth-on-token-expiration)?

this was actually by design to ensure the `ts-force-gen` always references the same version of ts-force as they have a strong co-dependency. It made releases much easier to deal with....

It should be possible, but unfortunately the documentation here is vague at best. Would need to dig into what the "Salesforce-provided CometD" `setReplay` code is actually doing. Looks like that...

ya, looks like it just wasn't pushed up. It's a minor change (upgrading axios) but has potential to break a lot of implementations that rely on axios features like interceptors....