up vote 0 down vote favorite
share [g+] share [fb]

Does anyone have a complete set of instructions on what needs to be done to Open Fire for it to support the Pandion client to connect with integrated windows authentication?

(Currently my Open Fire server works fine for Spark, and is using the AD accounts but Pandion can't connect)

link|improve this question
88% accept rate
feedback

closed as too localized by voretaq7♦ Feb 6 at 6:22

This question is unlikely to ever help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. See the FAQ for guidance on how to improve it.

1 Answer

up vote 0 down vote

Pandion connected to my openfire server with no special configuration. The only thing was that I had to enter my username as username@openfiredomain not just username as in spark et. al.

In my case it was the name of the server that was the configured domain, so "mark@openfire.local" but you will need to find your own domain value in the openfire config.

Also make sure you alter the connection settings on the Pandion logon screen to point to your openfire server ip or hostname.

link|improve this answer
His question was about single sign on which you need to patch openfire for NTLM support in order for this to work. It is not as simple as just entering the user name. – Kyle Nov 1 '11 at 16:48
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.