powered by Jive Software

Exterraneous users can''t be removed

I have just done an install of Wildfire 2.4.2 on an internal server using the included database protocol (I was going to use MySQL, but that resides on the same server, so I don’'t feel that there would be THAT much of a performance gain).

When I look at the users in the Admin Console, I have 500 users that don’'t exist (only 3 have registered on the server so far for testing).

When I try to remove them, I get a message:

java.lang.UnsupportedOperationException: User provider is read-only.

at org.jivesoftware.wildfire.user.UserManager.deleteUser(UserManager.java:121)

at org.jivesoftware.wildfire.admin.user_002ddelete_jsp._jspService(user_002ddelete _jsp.java:90)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:822)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:813)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:43)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:813)

at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:813)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:813)

at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:494)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:569)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:624)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1434)

at org.mortbay.http.HttpServer.service(HttpServer.java:896)

at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)

at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)

at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)

at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:366)

at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

I’‘m guessing that there’'s a lock somewhere in the datastore, but where can I find it to remove it and zap these users?

Hey AlexDeGruven,

Are you using LDAP? It sounds like the users that you are getting came from LDAP. Moreover, when using LDAP the way to delete users is from the LDAP server (or LDAP client).

Regards,

– Gato

That’‘s the strange thing, but a lot of the users I’‘m seeing in the list are not LDAP entities, but that’'s something I can look into.

What’'s strange is that I"m only seeing 500 accounts, but our LDAP (Novell eDirectory) has over 15,000 entities, so I should be seeing something along those lines.

Looks like LDAP is it. I looked further into the accounts, and all of them are entities within our eDirectory.

Thanks for your help!

Accounts are only populated from LDAP into Wildfire after they login for the first time.

Alex