Hello,
I'm using Alfresco Community 6.1 with Keycloak. It's all working fine but from time to time after I leave my PC for a longer period of time I get a "communication failure" Error displayed in Alfresco Share. When I refresh the page I am redirected to the login page (because the auth token has expired) but it should auto-redirect me instead of displaying the error.
I noticed this error comes from the handleTransactionResponse() method in the connection.js file, YUI library. Is there a way to override this method to add the location.reload() line? Or is there any better solution?
Normally, there should already be a default handling of 401 response errors from Share / the backend to reload the page, which should give you the login page. Since I have never used Alfresco's default Keycloak integration (which I consider to be naiive / too minimalistic), I don't know whether they managed to mess something up handling this kind of error, so that a 401 of the backend is masked somehow to the client, resulting in the 401 handling not being triggered.
Well, sometimes it redirects me directly but sometimes when i.e. PC is wakened up from sleep mode and the token has expired it just shows the error so it must be some kind of a bug.
Anyway, do you know how can I inject the small piece of code which would reload the page? I do not want to override the whole YUI library package just to change one method.
And to be honest, I'm using your alfresco-keycloak addon - it's really great! And I'm looking forward to your Tech Talk Live soon
Can @afaus help ?
Need immediate paid technical support for Alfresco community edition :
@ankitmodi89 Nice spamming 6 threads with the same question in the last 24h.
It's a community, everyone's here because of the will to help others. For customers with paid support I believe there is another place (Jira?).
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.