We are converting over to Windows Authentication. Everything seems fine, but if a user hits return when prompted for their credentials I am seeing a user with in Pulse described as "NT Authority\Anonymous with Public access.
How can this prevented?
Hi @regis.roethlein,
If they are being prompting for their user name that normally means there is an issue. The NT Authority\Anonymous means Pulse couldn’t work out who the user is. Is the Pulse service running under a network account rather than Local System?
If the user enters their id and Windows password, they are correctly logged in. It’s just when they do not fill in the login prompt at all and hit enter, they’re logged in as anonymous. Also, is a specific configuration required to have the login NOT prompt for the user’s id and password? The Pulse services are running as a domain account (not Local System
Hi Regis,
You should not need to login when Windows Authentication is on (Setting Up Windows (SSO) Authentication for Pulse - Cubewise CODE).
Could you please try to add the Pulse URL has as a trusted site in your internet options?
I hope this help,
Cheers,
Vincent
I know this thread is a couple of years old, but I thought I’d chime in with some potential solutions. As for your issue with Pulse and Windows Authentication, it sounds like hitting return when prompted for credentials is causing the user to be logged in as ““NT Authority\Anonymous with Public access.”” One potential solution could be to modify the Pulse settings to disable anonymous access. That way, users will be required to enter their credentials and won’t be logged in as anonymous.
Also, have you tried checking out Reddit Windows Key for any info or advice? There might be some helpful threads there.