Pandion seems to have stopped working on the client, anybody in here that can recommend another good client?? Spark uses java ane therefor a lot of RAM

Auto-reconnect should “just work”, if it doesn’t then follow up on the Pandion support forums.

So your saying an Openfire Server on a Windows box with Pandion clients, is it possible to get auto reconnect to work with Pandion?

Agreed, there’s a lot that the Pandion guys should be working on. It half sounds (from the Pandion forums) like there might be a christmas release with some updates. Pandion is/was the only client that does NTLM auth, when I was testing Spark didn’t yet have that capability natively (in fact I’m not sure if it has even support for it yet).

In a larger enterprise it is much easier to deploy customised versions of Pandion, because you’re more likely to have an Systems Management Server around that can push MSI updates directly to client machines. Pandion doesn’t have official MSI’s, but there are a few unofficial ones available.

One minor downfall is that Pandion does not do an auto reconnect to a downed or restarted Wildfire Server. It can be tweaked to do this but in a large Enterprise this may not be doable. The latest version of Spark client has the auto reconnect implemented and also is distributed in an MSI installed package which is great for Group Policy based installations.

Sounds like you broke the configuration settings. Send me a copy of your config files via email, or get hold of me via jabber.

I’m using your wildfire-sasl-sspi.v4

Debug log:
2006.08.26 23:47:28 No AuthorizationProvider’s found. Loading DefaultAuthorizationPolicy
2006.08.26 23:47:28 tempus@MAIN not authorized to tempus

[Nurm: I stripped the other logs that are not required]

Thanks for the answer! It is very a pity, we’ll wait And I so hoped…

Unfortunately as you’ve found Wildfire 3.x doesn’t like my SSPI library. There will have to be a plugin written to enable non-standard authentication mechanisms (i.e. NTLM that Pandion supports). Spark is supposed to be supporting Kerberos (which Wildfire is supporting as a standard authentication mechanism)

What about Wildfire 3.0.1 for Windows? Pandion 2.5 + Wildfire 3.0.1 = Single-Sign-On fault

:’(