When accessing the relevant site you need to make sure you run Firefox as the Windows user you want to log on as. If you always log onto a workstation as a domain user then
there is no issue, otherwise you may need to Shift +
right-click the shortcut and choose Run as different user..., or setup a shortcut with your credentials saved
In Firefox, type about:...
To authenticate Firefox automatically through a proxy (avoiding NTLM prompt), you have to modify 3 parameters.
Open the page about:config (in the address bar)
Add your uris (separate with ,) in the following 3 parameters:
and change it with ...
Start with the Enterprise deployment article.
First write the following to \Program Files\Mozilla Firefox\defaults\prefs\autoconfig.js:
Then put your actual settings in \Program Files\Mozilla Firefox\mozilla.cfg.js:
// the first line must be a comment
This worked for me:
network.automatic-ntlm-auth.allow-non-fqdn to True
and signon.autologin.proxy to True
Add yourcompanyname.com in:
Traditionally, Kerberos has used reverse-DNS to canonicalize the principal name. That is, after resolving targethost.example.com to an IP address, it tries to resolve the address back to the "canonical" name, and uses that for the principal.
If your targethost was resolved via /etc/hosts, then the first name in the corresponding line will be used as the "...
Though the IP addresses and hostnames associated with the secondary network interfaces have corresponding A and PTR records in DNS, there is no "enrollment" of the IP addresses and hostnames associated with the secondary network interfaces in Kerberos.
Well, do enroll them.
On each multihomed server, disable strict principal checking and tell it ...
This is possible for Windows 10 clients with Azure AD join which are also joined to a domain. In this case the client has SSO to all resources that are trusted by the on-prem DC, and also to the resources trusted by Azure AD.
For older clients, it depends. If you have ADFS, you will get full SSO for all on-prem and cloud resources. If you don't, you will ...
No, you cannot have single sign-on RD session between to client operating systems (Windows 7). The minimum requirement for single sing-on is between a client machine to the windows server or windows server to server. Because, the single sign-on RD session authentication is only available in the Server operating systems, not with client operating systems. So ...
I modified signon.autologin.proxy to be true (by double-clicking on the preference name) and changed network.negotiate-auth.trusted-uris to timecard.example.com and it's working for me, almost too well. When I sign out of the page, it takes me to a sign-in screen, where I'm instantly logged in again. But I can live with that. What is missing is a way to ...