You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vitaliy Biryukov (JIRA)" <ji...@apache.org> on 2019/01/25 12:45:00 UTC
[jira] [Updated] (IGNITE-11086) IGNITE_REST_SECURITY_TOKEN_TIMEOUT
parameter is set in deciseconds instead of seconds.
[ https://issues.apache.org/jira/browse/IGNITE-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaliy Biryukov updated IGNITE-11086:
--------------------------------------
Description:
According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should be set in seconds.
Can be fixed by multiplying this parameter by 1000 instead of 100 in GridRestProcessor's constructor:
{code:java}
sesTokTtl = IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT, DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
{code}
was:
According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should sit in seconds.
Can be fixed by multiplying this parameter by 1000 instead of 100 in GridRestProcessor's constructor:
{code:java}
sesTokTtl = IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT, DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
{code}
> IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of seconds.
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-11086
> URL: https://issues.apache.org/jira/browse/IGNITE-11086
> Project: Ignite
> Issue Type: Bug
> Components: rest
> Affects Versions: 2.7
> Reporter: Vitaliy Biryukov
> Priority: Major
>
> According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should be set in seconds.
> Can be fixed by multiplying this parameter by 1000 instead of 100 in GridRestProcessor's constructor:
> {code:java}
> sesTokTtl = IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT, DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)