We are having some problems with Resource Policy on an Openfire 3.3.1 server install on Windows using AD for authentication. We have this same exact setup on an old Wildfire 3.0.0 server which is currently servicing our production environment. The plan is to upgrade to Openfire 3.3.1. To test things out first, though, I did a new Openfire install in a test environment. All seems to work pretty well except or Resource Policy.
We have the “Always kick” policy setup on both our old Wildfire server and on this new test server. It works right on our Wildfire server. When a person logs in somewhere else, their first connection gets the boot. On Openfire, though, the old connection stays connected. It doesn’‘t matter if I choose “Always kick”, or “Never kicks” – two of the same account can get on at once. I’'ve tried to compare settings bit for bit between both servers and they are identical where applicable. Can anyone help me figure out why Resource Policy is not working properly on Openfire, but it is on Wildfire?