Messages Fail Only When Using auto_login

[theplaceilive]

Hoping you can help. I'm running Openfire 4.7.5 with inVerse 10.1.4 Release 1. Thanks!

I have inVerse installed and everything works fine when manually logging in. Once logged in, the webpage shows accurate contact status and I'm able to send and receive messages. Everything works fine when my index.html file contains converse.initialize({ config })

However, I'm unable to send or receive messages when I attempt to use auto_login. My web user is successfully automatically logged in, contact status is accurately presented on both the web interface and my internal Spark clients, but messages can't be sent or received. The message portion of the webpage simply turns gray when attempting to send a typed message. Sending a message from an internal Spark user to the logged in web user is also not received even though the web user status within Spark shows the web user as available.

The following reflects the initialization options used with this condition. I've tried many variations with the same results. The condition described only happens when using auto_login. Again, manually logging in works fine.

            converse.initialize({
			show_controlbox_by_default: true, 
			auto_list_rooms: true,
			bosh_service_url: 'https://chat.myserver.com/http-bind/',
			authentication: 'login',
			auto_login: true, 
			auto_subscribe: true,
			allow_logout: false,
			prebind: false,
			jid: '[email protected]', 
			password: 'mypassword',
			reuse_scram_keys: true, 
			keepalive: true,
			auto_away: 360, 
			auto_xa: 600, 
			auto_reconnect: true, 
			auto_subscribe: true,
			message_archiving: 'always',
			allow_otr: true, 
			cache_otr_key: true, 
			sticky_controlbox: true, 
			view_mode: 'fullscreen',
			show_message_avatar: true,
			use_otr_by_default: true
			});

[guusdk]

I wonder if this is a problem in Converse (the third-party, web-based XMPP client that is embedded by the inVerse plugin), rather than in the Openfire plugin itself. The Openfire plugin doesn't really do much, to be honest. @jcbrand, do you happen to know if the auto_login feature is working properly in 10.1.4?

[theplaceilive]

Thank you for the response.

It appears it is an issue with the version of Converse. I removed my local settings and specified CDN based entries as shown for 10.1.5. The auto_login feature now works.

<link rel="stylesheet" type="text/css" media="screen" href="https://cdn.conversejs.org/10.1.5/dist/converse.min.css">
<script src="https://cdn.conversejs.org/10.1.5/dist/converse.min.js" charset="utf-8"></script>

FYI; I tried specifying the newly released 10.1.6 version within the CDN settings and auto_login again fails, but it works fine with 10.1.5.

[jcbrand]

do you happen to know if the auto_login feature is working properly in 10.1.4?

I'm not aware of any issues with it.

[theplaceilive]

I found 10.1.4 auto_login does automatically log the user in. However, messages can't be sent or received even though the status of other users is accurately presented. The same symptom is experienced when using auto_login on 10.1.6. I tested on both 10.1.4 and 10.1.6 many times.

Messages can be sent and received just fine when "manually" logging in on 10.1.4 and 10.1.6. The problem is only experienced when auto_login is used.

I'm successfully using 10.1.5 with auto_login. Everything works as it should.

[jcbrand]

I believe you, but there isn't enough information for me to come to any kind of conclusion. I don't see how auto-login is related to whether messages can be sent or not.

[theplaceilive]

Seems very odd to me also.

I've tried it countless times with the initialization parameters listed above and the symptoms as described happened every time, but only on 10.1.4 and 10.1.6. The only item of interest in my environment is I use Caddy as a Reverse Proxy for external visitors, but it also failed when used internally when auto_login with 10.1.4 or 10.1.6 was used.

However, everything works just fine with auto_login on 10.1.5 both internally and when accessing externally with Caddy serving as a Reverse Proxy. It's been flawless and I can easily make it fail again by changing back to 10.1.4 or 10.1 6.

You may want to try it yourself just to prove it one way or the other.