This behavior is correct since you have set the token validity as 60s. After one minute the token is invalid.
On Thu, Mar 6, 2014 at 11:03 AM, Asanthi Kulasinghe <[email protected]>wrote: > > Hi, > > Can someone explain the behaviour of > <EnableOAuthCache>true</EnableOAuthCache> , in identity.xml of API-Manager. > > Does it have an impact on the token expiration time? > > With the following configurations, my token expires exactly after 60 > seconds, even if the API has been invoked before the expiration. > > identity.xml : > > <UserAccessTokenDefaultValidityPeriod>60</UserAccessTokenDefaultValidityPeriod> > <TimestampSkew>0</TimestampSkew> > <EnableOAuthCache>true</EnableOAuthCache> > > api-manager.xml : > <EnableKeyMgtValidationInfoCache>false</EnableKeyMgtValidationInfoCache> > <EnableKeyMgtValidationInfoCache>false</EnableKeyMgtValidationInfoCache> > > Is this correct or should the token be cached for the default duration of > 15 mins since <EnableOAuthCache> is set to true? > > Regards > > *Asanthi Kulasinghe* > Software Engineer - QA > WSO2 Inc; http://www.wso2.com/. > Mobile: +94777355522 > > > -- Thanks & Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
