Pulse Secure Article: KB43961 - "Lock down this connection" option is automatically disabled after selecting Save Changes in Pulse Connect Secure 9.0R3
![Token2 | MFA tokens OATH-TOTP SHA-1 SHA-256 | Using Token2 programmable TOTP hardware tokens with PulseSecure Connect | TOKEN2 MFA Products and Services | programmable hardware token, FIDO2 key, U2F key, TOTP, Token2 | MFA tokens OATH-TOTP SHA-1 SHA-256 | Using Token2 programmable TOTP hardware tokens with PulseSecure Connect | TOKEN2 MFA Products and Services | programmable hardware token, FIDO2 key, U2F key, TOTP,](https://www.token2.com/img/pcs/pic6.png)
Token2 | MFA tokens OATH-TOTP SHA-1 SHA-256 | Using Token2 programmable TOTP hardware tokens with PulseSecure Connect | TOKEN2 MFA Products and Services | programmable hardware token, FIDO2 key, U2F key, TOTP,
Pulse Secure Article: KB40250 - AAA/SignIn URL: How to prevent users from browsing to other sign-in policies by changing the sign-in URL index value
Pulse Secure Article: KB40363 - Behavior of "Lock Down this connection" (also known as Lock Down Mode)
Why am I seeing the error "Primary authentication failed" when logging into the Juniper/Pulse web portal?
![Token2 | MFA tokens OATH-TOTP SHA-1 SHA-256 | Using Token2 programmable TOTP hardware tokens with PulseSecure Connect | TOKEN2 MFA Products and Services | programmable hardware token, FIDO2 key, U2F key, TOTP, Token2 | MFA tokens OATH-TOTP SHA-1 SHA-256 | Using Token2 programmable TOTP hardware tokens with PulseSecure Connect | TOKEN2 MFA Products and Services | programmable hardware token, FIDO2 key, U2F key, TOTP,](https://www.token2.com/img/pcs/pic16.png)