<?xml-stylesheet type="text/xsl" href="https://community-ppe.thomsonreuters.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Access token expiration change in Collaborate 5.2</title><link>/developer/b/announcements/posts/access-token-expiration-change-in-collaborate-5-2</link><description>From Collaborate version 5.2 the option to set access token expiration for three months, six months or a year will be removed. The reasons for this are:	to avoid situations where an access token and refresh token both expire at the same time	bec...</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Access token expiration change in Collaborate 5.2</title><link>https://community-ppe.thomsonreuters.com/developer/b/announcements/posts/access-token-expiration-change-in-collaborate-5-2</link><pubDate>Tue, 13 Aug 2019 09:43:00 GMT</pubDate><guid isPermaLink="false">40c2cb25-c969-4af9-8105-afc9e3de7355:dcc7c408-fe9a-4bcb-baaf-bfc20e83578f</guid><dc:creator>Imran Aziz</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Since posting this announcement we have discussed this change with few integrators and they have confirmed compliance with the integration standard. If any integrator has any concerns with this change then please comment on this post.&lt;/p&gt;

&lt;p&gt;Please note that refresh token implementation is a required feature of our API compliance standard, and we request all integrations to use refresh token to comply with security standards.&lt;/p&gt;

&lt;p&gt;Thank you.&lt;/p&gt;
&lt;img src="https://community-ppe.thomsonreuters.com/aggbug?PostID=885&amp;AppID=167&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>