Repository navigation
Replies: 1 comment 2 replies
|
I don't think this is currently possible. Jumpstart doesn't do native authentication anymore, everything is handled via web views. So the cookie when signing in is used (without developer intervention) for future Hotwire Native web requests. If I have to implement native auth screens for clients I recommend no API token. Instead, I send a cookie in the JSON response that I then copy over to WebKit world for Hotwire Native to use automatically. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In our iOS native app using Hotwire, we manage user sign-in through native screens and securely store the API token in the Keychain.
Setting API Token for Hotwire Requests: How can we configure Hotwire to include the API token (retrieved from the Keychain) in all requests for HTML page views? Specifically, how do we attach the token to request headers or authenticate Turbo-driven HTML content? Are we extending a base HTTP library, or is there a setter method or configuration in a Hotwire/Turbo class that handles this?
Code examples or references to relevant Hotwire/Turbo iOS documentation would be greatly appreciated!
It seems JumpStartPro is doing what I'm asking.
All reactions