If it would be so easy, we would already have solved it. The problem is not that Jitsi assumes no connection=wrong credentials. @cassioac most likely uses or used Openfire. Jitsi only clears the credentials when the server reports that these are invalid, which also explains the situation with the AD server rebooting.
Simply not having a connection to the server definitively does not trigger clearing the password. I have never experienced this, but I would have on the countless WiFi hotspots which need an acknowledgment on a landing page. Or with the recent internet connection blackouts I had due to a broken cable modem.
If anyone wants to take a look at the "oneliner": start debugging at https://github.com/jitsi/jitsi/blob/master/src/net/java/sip/communicator/impl/protocol/jabber/ProtocolProviderServiceJabberImpl.java#L644
If someone can me provide me with an environment that allows reproducing the issue I can and will look at it.
You are receiving this because you commented.
Reply to this email directly or view it on GitHub: