Hi,
We have observed that the token expiration times in a API-Manager Clustered
set up for token types Application access token and User access token, are
taken from the values set in 2 different nodes.
ie:
value of the Store node's
identity.xml is considered for Application access token expir
The reason for this issue is, in API store when we generate token default
validity time will pick from store nodes config file. Then you will see
store nodes validity period(configured in identity.xml) in token validity
period box. But if you send token generation request(user access token) to
key
Hi Sanjeewa,
Ain't it a wrong design? IMO if the APPLICATION TOKEN is generated in the
KeyManager node (which you configure the server url in the store), then it
should read the validity period from the key manager node itself at the
time of token generation. I dont understand why it reads the v
On Mon, Jul 28, 2014 at 11:44 AM, Nirodha Pramod wrote:
> Hi Sanjeewa,
>
> Ain't it a wrong design? IMO if the APPLICATION TOKEN is generated in the
> KeyManager node (which you configure the server url in the store), then it
> should read the validity period from the key manager node itself at
On Sun, Jul 27, 2014 at 11:56 PM, Dinusha Senanayaka
wrote:
>
>
>
> On Mon, Jul 28, 2014 at 11:44 AM, Nirodha Pramod wrote:
>
>> Hi Sanjeewa,
>>
>> Ain't it a wrong design? IMO if the APPLICATION TOKEN is generated in
>> the KeyManager node (which you configure the server url in the store), th
Hi Dinusha,
Let me clarify my question. If the token is generated by the keymanager
node why does not that node itself set the validity period read from KM
node's identity.xml, at the time of token generation. Why does KM node
generate the token and store node sets the validity period. Why not KM
