[
https://issues.apache.org/jira/browse/USERGRID-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey updated USERGRID-213:
------------------------------
Sprint: (was: Double Check)
> inconsistent api when setting ttl for token
> --------------------------------------------
>
> Key: USERGRID-213
> URL: https://issues.apache.org/jira/browse/USERGRID-213
> Project: Usergrid
> Issue Type: Improvement
> Components: Stack
> Reporter: Strong Liu
> Priority: Minor
>
> found a problem when I'm working on a JIRA about setting ttl for a token
> the token expires time is returned in SECONDs, but the ttl property used in
> acquire a token is required in MILLISECOND which really confused me.
> And also, if the ttl value in request is less then 1000 (1s), the method
> _org.apache.usergrid.security.tokens.cassandra.TokenServiceImpl#calcTokenTime_
> will resolve is to 0, which in turn, this exception gets thrown
> me.prettyprint.hector.api.exceptions.HInvalidRequestException:
> InvalidRequestException(why:ttl must be positive)
> I know it probably means nothing when set the ttl less then 1s, but we
> probably need to make some change about this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
