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 manager through gateway then it will eventually hit key manager. Then validity period in key manager will effect. There is no logical reason for this. We need to add this configuration to all nodes in same way.
Thanks, sanjeewa. On Sun, Jul 27, 2014 at 10:56 PM, Asanthi Kulasinghe <[email protected]> wrote: > 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: > <ApplicationAccessTokenDefaultValidityPeriod> value of the Store node's > identity.xml is considered for Application access token expiration time. > <UserAccessTokenDefaultValidityPeriod> value of the Key Manager node's > identity.xml is considered for the User access token expiration time. > > Is there a logical reason behind this or should the values set in Key > Manager node be considered for both token types? > > Regards > *Asanthi Kulasinghe* > WSO2 Inc; http://www.wso2.com/. > Mobile: +94777355522 > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
