TurboVNC Authentication issues:

Hi,
I have installed TurboVNC (turbovnc-2.1) on my RHEL 6.7 server and used permitted-security-types = TLSPlain,X509Vnc. Now able to access my VNC session but observed below issues.
1) I am able to login to my VNC session with my paasword as well as with wrong passwords.
ex:My password:1234
Wrong password 1234567 or 678432
2) My colleagues also can able to access my VNC session with their credentials.
Please help me on this where I have done wrong configuration, What steps need to be taken to fix these issues.
Note:I am using NIS account.

This is a patch tracker, meant only for patch submissions, not for bug reports or feature requests. We do not use SourceForge to track bug reports/feature requests anymore. In the future, please post all bug reports/feature requests to GitHub rather than trying to subvert our project's wishes by posting bug reports where they do not belong.

I cannot reproduce the issue you are describing. Please post the contents of your /etc/pam.d/turbovnc file. Also please specify which VNC viewer you are using and how you are launching the TurboVNC Server.

Hi,

Thanks for your quick response.
Please find the below details.

$cat /etc/pam.d/turbovnc

%PAM-1.0

auth include system-auth
account include system-auth
password substack system-auth
-password optional pam_gnome_keyring.so

using Vncviewer.jar, once open the VNC viewer there is option to enter the VNC server with port number, after that entering the VNC credentials.

I have no idea, unfortunately. I duplicated the settings in your /etc/turbovnc-security.conf file, as well as your /etc/pam.d/turbovnc file, and it works fine for me on CentOS 6.8. Maybe NIS is causing the problem. If not, then I'm clueless. The symptoms of the problem would suggest some sort of issue with PAM authentication, but PAM user/password authentication is used by thousands of other TurboVNC users around the world, and no one else has reported a problem like this. TurboVNC works fine with the default PAM settings on RHEL 6. Perhaps one of your other PAM files, such as system-auth, is the culprit.

Closing this tracker item. If you discover what the problem is and believe it to be something that could be worked around in TurboVNC, then please file a bug report or feature request on GitHub. Also feel free to add any findings here, if you want others who are having similar problems to be able to find the solution in Google searches.