package: x2gobroker priority: bug
Context : I'm using PAM auth with the X2Gobroker which relies on Samba/Winbind to use ActiveDirectory based authentication. It works pretty well but some users couldn't auth even though we triple checked their username/password combination. It appears these users had some accentuated characters in their password so I suppose there is a charset issue there, not sure if the broker uses iso/latin encoding or UTF8.
Regards, Walid Moghrabi
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you
Hi Walid, hi all,
On Mi 13 Dez 2017 19:29:07 CET, Walid MOGHRABI wrote:
package: x2gobroker priority: bug
Context : I'm using PAM auth with the X2Gobroker which relies on
Samba/Winbind to use ActiveDirectory based authentication. It works pretty well but some users couldn't auth even though we
triple checked their username/password combination. It appears these users had some accentuated characters in their
password so I suppose there is a charset issue there, not sure if
the broker uses iso/latin encoding or UTF8.Regards, Walid Moghrabi
I will work on this in the second week of January on a contracted basis.
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Hi Walid,
On Mi 13 Dez 2017 19:29:07 CET, Walid MOGHRABI wrote:
package: x2gobroker priority: bug
Context : I'm using PAM auth with the X2Gobroker which relies on
Samba/Winbind to use ActiveDirectory based authentication. It works pretty well but some users couldn't auth even though we
triple checked their username/password combination. It appears these users had some accentuated characters in their
password so I suppose there is a charset issue there, not sure if
the broker uses iso/latin encoding or UTF8.Regards, Walid Moghrabi
Regarding the above issue, can you please test, if an authentication
via the test tool works?
Steps:
Make sure the x2gobroker-authservice is running
x2gobroker-testauth --user=<user>
(Password is queried then after having hit <ENTER>.
Does that work? Or does this also fail? (Here it works).
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Hi,
Just re-tried and now it works. Dunno if something has been fixed since when I declared the bug ... maybe the upgrade to Python3.
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Mike Gabriel" <mike.gabriel@das-netzwerkteam.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu>, 1240@bugs.x2go.org Envoyé: Lundi 12 Février 2018 16:52:16 Objet: Re: [X2Go-Dev] Bug#1240: broker bug with accentuated characters in password
Hi Walid,
On Mi 13 Dez 2017 19:29:07 CET, Walid MOGHRABI wrote:
package: x2gobroker priority: bug
Context : I'm using PAM auth with the X2Gobroker which relies on Samba/Winbind to use ActiveDirectory based authentication. It works pretty well but some users couldn't auth even though we triple checked their username/password combination. It appears these users had some accentuated characters in their password so I suppose there is a charset issue there, not sure if the broker uses iso/latin encoding or UTF8.
Regards, Walid Moghrabi
Regarding the above issue, can you please test, if an authentication via the test tool works?
Steps:
Make sure the x2gobroker-authservice is running
x2gobroker-testauth --user=<user>
(Password is queried then after having hit <ENTER>.
Does that work? Or does this also fail? (Here it works).
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you
Control: tags -1 pending Control: fixed -1 0.4.0.0
Hi Walid
On Mo 12 Feb 2018 18:38:21 CET, Walid MOGHRABI wrote:
Just re-tried and now it works. Dunno if something has been fixed since when I declared the bug ...
maybe the upgrade to Python3.
Ok. Let's consider this issues resolved by the Python3 switch (which
makes strings Unicode strings -- always).
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Processing control commands:
tags -1 pending Bug #1240 [x2gobroker] broker bug with accentuated characters in password Added tag(s) pending. fixed -1 0.4.0.0 Bug #1240 [x2gobroker] broker bug with accentuated characters in password There is no source info for the package 'x2gobroker' at version '0.4.0.0' with architecture '' Unable to make a source version for version '0.4.0.0' Marked as fixed in versions 0.4.0.0.
-- 1240: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1240 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems