Allow user specific token lifespans

[codez]

Instead of keeping the token lifespan only in the global configuration, we added a corresponding method in the User Module. This method may be overriden to return a user specific value for the token lifespan. By default, the global value is used.

Use case: We have users working all day with the application in the company headquarters, who do not want to login after short breaks. Other users access the application just for a few minutes from public computers, for whom we prefer to have a very short token lifespan.

[MaicolBen]

Good work, but seems a specific use case of this gem, I don't know if everyone wants that. Don't you need a migration for this?

[codez]

That's why I implemented the default token_lifespan method of a User it in an unobtrusive way. The behavior remains the same if you do not want to use this feature. You do not have to care in this case.

If the feature is used, it is left to the programmer to provide a decent implementation for this method. The most obvious case is an accessor method for a database column, and the a migration would be needed. But it really might be anything, so the programmer has full flexibility.

[zachfeldman]

Seems fairly straightforward, especially if it doesn't impact default behavior.

[MaicolBen]

Yeah, this gives more flexibility. I checked and resource isn't null everywhere you replaced the default behavior.

[zachfeldman]

👍 we should cut a release soon...