bkleven
Show profile
Link to this post
Subject: Support for XEP-0106 (JID Escaping)
Hello everyone - I'm new to Psi. So far, I like the blend of features and UI design quite a bit, and I also like the stability (I've had some crashing issues with Gajim).
One problem I do have, though, is that our company has set up our LDAP uid's as '<firstname> <lastname>' - that's right, there's a space in our UID.
We needed to set up a Jabber server for our site, and for many reasons, we needed to use our LDAP accounts for login. This creates JIDs with spaces, which then have to be escaped to become valid JIDs.
Our server handles this well (Openfire), but client support varies. For manual buddy list management, Psi can handle JIDs that look like this:
<firstname>\20<lastname>@<host>[/<resource>]
The problem is that the search feature in Psi receives the results from the server just fine but does not replace the space in the JID that it creates in order to make it valid, so the JID cannot be added to the buddy list from the search results. It still has to be added manually.
I haven't used Psi that much yet, so there may be other parts of the app that have issues with these illegal JIDs that need escaping, but I haven't seen them.
I hope this is not a repeat request - I checked several places in the forum and roadmap and did not see any mention of XEP-0106. My apologies if this is being addressed.
Thank you for creating a great Jabber client! I look forward to future versions - it looks like there are some great features on the roadmap.
One problem I do have, though, is that our company has set up our LDAP uid's as '<firstname> <lastname>' - that's right, there's a space in our UID.
We needed to set up a Jabber server for our site, and for many reasons, we needed to use our LDAP accounts for login. This creates JIDs with spaces, which then have to be escaped to become valid JIDs.
Our server handles this well (Openfire), but client support varies. For manual buddy list management, Psi can handle JIDs that look like this:
<firstname>\20<lastname>@<host>[/<resource>]
The problem is that the search feature in Psi receives the results from the server just fine but does not replace the space in the JID that it creates in order to make it valid, so the JID cannot be added to the buddy list from the search results. It still has to be added manually.
I haven't used Psi that much yet, so there may be other parts of the app that have issues with these illegal JIDs that need escaping, but I haven't seen them.
I hope this is not a repeat request - I checked several places in the forum and roadmap and did not see any mention of XEP-0106. My apologies if this is being addressed.
Thank you for creating a great Jabber client! I look forward to future versions - it looks like there are some great features on the roadmap.
![[Image: http://machekku.uaznia.net/jabber/jobble/map/jmpixel1.png]](http://machekku.uaznia.net/jabber/jobble/map/jmpixel1.png "http://machekku.uaznia.net/jabber/jobble/map/jmpixel1.png"){kind=tracking}
