On Wednesday, September 10 Aidin made a DNS change to allow it's primary application, Next, to service traffic from the installed Aidin printer that many customers use to send documents to Aidin. According to our usage data this cutover was seamless for most users. A small number of users could no longer authenticate after the cutover due to a confluence of factors that included their organization's session timeout settings and the specific version of the embedded browser available to the Aidin printer for the single sign on workflow on the client.

For many users who encountered this issue, clearing authentication cookies solved the problem. Aidin has since released a server patch that resolves the issue for remaining users. During our investigation we discovered a discrepancy between session timeouts for the now-deprecated installed printer service and our web application. Now that the two services are better aligned your users may need to authenticate more often than the previously were, but in alignment with your organization's configured session timeouts.