[
https://issues.apache.org/jira/browse/USERGRID-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Shelley updated USERGRID-750:
-------------------------------------
Description:
If I send a PUT request to set the accesstokenttl to 0 for an app:
{code}
{
"accesstokenttl": 0
}
{code}
And then make a subsequent client_credentials token request, the token ttl in
the response is still 604800:
{code}
{
"client_id": "***",
"client_secret": "***",
"grant_type": "client_credentials",
"ttl": 0
}
{code}
Response:
{code}
{
"access_token": "***",
"expires_in": 604800,
"application": "***"
}
{code}
[~tnine] suggests this may be a response rendering problem and that it is
actually setting the expiration correctly in the stack.
was:
If I send a PUT request to set the accesstokenttl to 0 for an app:
{code}
{
"accesstokenttl": 0
}
{code}
And then make a subsequent client_credentials token request, the token ttl in
the response is still 604800:
{code}
{
"client_id": "***",
"client_secret": "***",
"grant_type": "client_credentials",
"ttl": 0
}
{code}
Response:
{code}
{
"access_token": "***",
"expires_in": 604800,
"application": "***"
}
{code}
[~tnine] suggests this may be a response rendering problem and that it is
actually setting the expiration correctly in the stack.
> When setting accesstokenttl to 0, client credentials auth still returns 604800
> ------------------------------------------------------------------------------
>
> Key: USERGRID-750
> URL: https://issues.apache.org/jira/browse/USERGRID-750
> Project: Usergrid
> Issue Type: Bug
> Components: Stack
> Reporter: Brandon Shelley
> Priority: Minor
>
> If I send a PUT request to set the accesstokenttl to 0 for an app:
> {code}
> {
> "accesstokenttl": 0
> }
> {code}
> And then make a subsequent client_credentials token request, the token ttl in
> the response is still 604800:
> {code}
> {
> "client_id": "***",
> "client_secret": "***",
> "grant_type": "client_credentials",
> "ttl": 0
> }
> {code}
> Response:
> {code}
> {
> "access_token": "***",
> "expires_in": 604800,
> "application": "***"
> }
> {code}
> [~tnine] suggests this may be a response rendering problem and that it is
> actually setting the expiration correctly in the stack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
