Skip to content
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.

Silent Login on Launch #30

Open
Vortec4800 opened this issue Jan 29, 2014 · 2 comments
Open

Silent Login on Launch #30

Vortec4800 opened this issue Jan 29, 2014 · 2 comments

Comments

@Vortec4800
Copy link

One thing that seems to be missing is a method that performs a "silent login" attempt on login using a previously saved auth token. Without this, the user would need to re-log in to the app every time it launches.

Is this on the roadmap? We may try to figure this out ourselves, just wasn't sure if you had a plan for it already.

@calebd
Copy link
Owner

calebd commented Feb 3, 2014

I'm not sure I know what you mean. Once you have a user token, you are permanently logged in. Save the token to the keychain and you will be able to make any request on behalf of the user. An exception to this is services like Facebook where tokens expire after a specified amount of time. For these, the token response contains an NSDate indicating when the token expires.

@Vortec4800
Copy link
Author

Yes, Facebook is what I was referring to specifically. Google does the same thing, though that doesn't apply here.

We added some functionality to re-auth a user given an old token, we'll send in a pull request so you can take a look.

rocket0423 added a commit to rocket0423/SimpleAuth that referenced this issue Feb 4, 2014
Added re-auth for tokens that expire by adding a new method that allows a user to pass in an existing token returning a new token with a later expiration date.  If provider does not have this method code reverts to the normal login method for provider. This fixes issue calebd#30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants