Installing OpenFire with MariaDB on CentOS 7
-
Vultr does enable the EPEL by default if memory serves. They also pre-update the OS to the very latest before install.
-
@scottalanmiller said:
Notice that the URL was changed to show the local IP address and the name that we selected earlier for the database "openfire".
Select MySQL from the dropdown.
The username and password are the ones that we set manually earlier.
Are the minimum and maximum connections the amount of users that will be connecting to it or is that something I don't even need to worry about?
-
Don't worry about it at your size. That's a stateless Apache connection tuning thing and very different from the number of potential users.
-
I am getting the same red banner across the top as in your screenshot. Says "A connection to the database could not be made. View the error message by opening the "/log/error.log" log file, then go back to fix the problem."
-
Post a screenshot of your configuration.
-
Never mind, I figured this out too!
They make you create too many users and passwords.... after a few different combinations, I was able to move forward. -
Is AD integration with SSO even worth considering?
-
@bbiAngie said:
Is AD integration with SSO even worth considering?
That TOTALLY depends on your specific environment.
-
I would think AD integration would be pretty nice - only one user DB to worry about, one less username and password for your users to remember, but SSO might not be worth it.
-
It has been a while since I've mucked around with OpenFire, but I was never able to get AD integration to work... Still, though... for 80 users... that might be worth tinkering around with.
-
I thought about it a little bit. There are some aspects of AD integration and SSO that totally make sense in out environment. However, I think I am going to stick with using the "vanilla" setup. I think in the end it will make the most sense. We have a few users that go by different names than their windows logins so it might be easier to just manually manage user creation and such.
-
My boss talked to me once about having a chat solution in the office for staff. But during the discussion she talked herself out of it thinking the staff would use it more for gossip than for work. Which is probably true.
That coupled with the fact that chat would take a lot longer to explain a problem to get help with than a phone call, but 90% of phone calls result in visiting the user anyway, so - really no point.
-
We use them constantly and love them but can't find one that really makes us happy.
-
I hate out messaging solution. The message history is awful, the interface looks like garbage and each message stacks in a new box on top of another instead of having a chat window.
We tried LAN messenger but didn't like that at all. So hopefully this gets us close to what we need. Only issue I see is that no on will log in so hopefully I can setup some auto login stuff on the client. -
Easy enough... I really like the Jitsi chat client. It works great with my chat server!
(Website: https://jitsi.org/) -
@bbiAngie said:
I hate out messaging solution. The message history is awful, the interface looks like garbage and each message stacks in a new box on top of another instead of having a chat window.
We tried LAN messenger but didn't like that at all. So hopefully this gets us close to what we need. Only issue I see is that no on will log in so hopefully I can setup some auto login stuff on the client.Look into doing it with AD and SSO. Then set it to startup when people log in. That way they won't have the remember a password or anything.
-
@bbiAngie said:
Only issue I see is that no on will log in so hopefully I can setup some auto login stuff on the client.
We used to do that with OpenFire, worked great.
-
A nice thing about OpenFire is that it is just an open source and open standards XMPP server. So you can use any XMPP/Jabber client that you like. It comes with Spark, but there are lots of options on every platform. Very flexible. And you don't have to use the same one everywhere.
-
@Reid-Cooper said:
A nice thing about OpenFire is that it is just an open source and open standards XMPP server. So you can use any XMPP/Jabber client that you like. It comes with Spark, but there are lots of options on every platform. Very flexible. And you don't have to use the same one everywhere.
Spark sucks and it's Java based on the client.. two strikes against it.
The only things going for it is it is the native client and openfire has plugins to control it and it's one of the fewer XMPP clients that supports SSO (there are 2 or 3 others that do with plugins).
-
What are your favorite clients? I am curious as to what people use. I am not sure my users are going to like spark. Looking for one that is stupid easy. My users like simple and plain and ZERO change. I can compromise with simple and plain, don't care if they don't like the change, its happening!
