RE: Access token expiration change in Collaborate 4.4 - On hold until later in the year

Robyn Tippins — Mon, 18 Jun 2018 17:29:00 GMT

Hi Andrew Quinn - please see our updated post above. This development has now been put on hold and we will keep you posted once anything changes.

RE: Access token expiration change in Collaborate 4.4 - On hold until later in the year

Imran Aziz — Mon, 11 Jun 2018 13:50:00 GMT

Andrew Quinn thank you for the prompt feedback I am going to discuss this internally to make sure that our API clients are not disrupted by this change. If there are any changes to what has been communicated they will be shared in the Developer Community.

RE: Access token expiration change in Collaborate 4.4 - On hold until later in the year

Andrew Quinn — Sat, 09 Jun 2018 04:38:00 GMT

Hi Imran Aziz,

I'd like to throw my hat into the ring first. I don't have concerns as to the why, but I do have concerns as to the when. With approx. 4wks to 4.4 being released, I feel that this change hasn't been communicated in a time relative to it's impact.

We utilise AWS Lambda's to run micro-services, using the Collaborate API. Lambda's by themselves do not have the capabilities for persistent storage - for that we'd need to leverage off S3 or DynamoDB, for example. We chose to adopt the manual token approach initially, to satisfy project timescales at the time, and to produce lean and efficient microservices. Now will need to rearchitect our services to gain persistent storage and use the refresh token mechanism, as well as factor this into our current deadlines - this was always to be a design decision to come back to, but one that we could factor into our long-term project timelines.

I also would like to ask how this impacts the Neota/Raven/Kira etc integrations? From what I remember of seeing the Neota prototype - I could be wrong here, or things have changed - it relied on a configured authenticated token. I don't remember seeing a refresh mechanism? Many of these integrations will be built from simple automated script-like interfaces, where again persisted storage has not been factored in.

Thanks in advance, Andrew