There should be no need to do additional configurations to make a Linux GUI such as Gnome or KDE or others to work with our authentication services.
In compatible distributions when you install Safeguard Authentication Services it automatically configures PAM modules in the equivalent /etc/pam.d directory and if exists the /etc/pam.conf file.
Any application that follows PAM API architecture will usually call /etc/pam.d/<module name> which in turn will usually call /etc/pam.d/password-auth and /etc/pam.d/system-auth.
By doing this all PAM-enabled applications in the system should have immediate access to the Safeguard services.
Note for Starling users:
When you log into a system via GUI, you will notice that you are prompted for your AD credentials and then the graphical login process waits for something to happen.
The pause is caused by the Linux GUI app waiting for the user to Accept/Decline the PUSH notification that was sent to his mobile unit (if configured) by our authentication services.
At GUI level, a user will not get the usual 3 options prompt (PUSH/PHONE/SMS).
This is due to the way GUI managers are written and many do not (yet) support the back and forth like pam / keyboard-interactive can. So we can't tell it to display our prompts hence our system defaults to a PUSH notification.