Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore hardcoded jwt #5

Merged
merged 3 commits into from
Feb 21, 2016
Merged

Conversation

shankari
Copy link
Contributor

No description provided.

…code

The original idea was that the javascript implementation of the code would just
use the javascript HTTP implementations, and make a call to the native code to
get the JWT. As we can saw, this does not refresh the token correctly if it is
expired, which is why we went back to the old hardcoded method.

But then if we want to use the old hardcoded method from javascript, we need to
make calls back to native code.

This change implements plugin interfaces on both ios and android that make the
appropriate calls to the native code, and change the javascript to call it
appropriately.

This has not yet been tested, but let's get an initial version checked in.
The iOS code still doesn't actually work. So there's at least one more checkin
coming in.
Basically, if the currAuth is NULL, then we read it from the keychain. But with
the previous structure, after reading it, we just exit since everything else
was in a giant else.

Now, once we read the currAuth, we use it in the rest of the code.
Wow. Simple restructuring. Much working.
shankari added a commit that referenced this pull request Feb 21, 2016
@shankari shankari merged commit 26d74c3 into e-mission:master Feb 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant