| Summary: | Cannot connect to password protected Jabber conferences. | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] telepathy | Reporter: | Gavin L McNabb <bgeuropefan> |
| Component: | general | Assignee: | Rohan Garg <rohan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ddomenichelli, kde, rohan |
| Priority: | NOR | ||
| Version: | git-latest | ||
| Target Milestone: | 0.6-next | ||
| Platform: | Chakra | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/telepathy-auth-handler/0ecb0a62cfa580a399e3928f13b04edcc42a6cc3 | Version Fixed In: | 0.6.0 |
| Attachments: | What should happen, same room. Psi (left) and Telepathy (right) | ||
Seems likely, I've not written anything that does it :-) I believe it's this channel that's relevant: http://telepathy.freedesktop.org/spec/Channel_Interface_Password.html and in TpQt4: http://telepathy.freedesktop.org/doc/telepathy-qt4/a00099.html Though they're the annoying low level bindings instead of the nice stuff. I'm not sure which part of the text-ui this belongs in, or whether this needs to happen before we create the ChatWidget with the channel. Hopefully we just implement this interface and everything works. I think although the code needs to go into the text-ui we should try and make it such that it can be re-usable as every type of channel (not just text) could have this interface. Maybe a class in the lib, that takes a channel as a parameter and subclasses pending operation that checks if the password interface exists, and takes appropriate UI action if needed. Does anyone know how to set up a password protected conference room which we can use for testing. If anyone else is up for coding this I'll guide them through (as I've just researched it), otherwise I'll do it when I find time. Just create a New room in Pidgin or any other Jabber client (simply join a nonexistent room), open the room control panel (type /config in Pidgin), and just add a password. Talking of which, there's the entire RoomConfig1 spec to implement.... Alternately maybe this channel should be handled by the auth-handler. Need to confirm what Empathy does. Working on this, have a rough implementation of things in my scratch repo. Should be ready by 0.6 Partial working implementation can be found in kde:scratch/garg/ktp-auth-handler . Clickable link : http://quickgit.kde.org/index.php?p=scratch%2Fgarg%2Fktp-auth-handler.git&a=shortlog&h=refs/heads/password_protected_rooms Branch is password_protected_rooms , a note of caution here, I will be rewriting history . In order to test : /opt/project-neon/lib/kde4/libexec/ktp-auth-handler --persist ( adjust according to install path, this is for testers using Project Neon ) -> Join a password protected room. |
Created attachment 66519 [details] What should happen, same room. Psi (left) and Telepathy (right) Version: git-latest (using KDE 4.7.3) OS: Linux When opening a Jabber conference that's protected with a password, you're presented with a blank chat screen. Reproducible: Always Steps to Reproduce: Login to Jabber, select Join chatroom, Enter Room Name, Blank chat appears Actual Results: Blank Chat appears Expected Results: The chatroom should open, see attachment for a side by side of Telepathy and Psi.