Update to the Authentication Policy Behavior for Remote Users

Your account is configured to use Registration Code as the user authentication method for the Cato Client. However, we have identified that some users can still authenticate with their username and password. 

On May 24, 2026, we will introduce a fix that enforces authentication by Registration Codes only, as per the original configuration.  

After this date, users will only be able to authenticate using a registration code and will no longer be able to authenticate with their username and password. 

What is the Impact to the Account? 

After May 24, 2026, users will no longer be able to authenticate to the Client with their username and password. Users who do not have a valid registration code may not be able to authenticate and connect to your network. 

What Action do I Need to Take?

The action required depends on how you want your users to authenticate. If you want users to:  

• Authenticate with a Registration Code, and they already have received a code – no action is required. 
• Continue authenticating with their username and password, either: 
  • Remove registration codes as the method of provisioning users and set your account level Authentication Method to User & Password.  
    This will to apply to all users, for more information, see Activating Users with a Registration Code and  Configuring the Authentication Policy for Cato Clients 
  • Update the authentication settings for specific users. For more information, see Configuring the Authentication Policy for Cato Clients. 
  • If you want users to authenticate with registration codes, make sure that users have valid registration codes. For more information, see Activating Users with a Registration Code. 

Who do I Talk to If I Have Questions? 

Please use the Cato Knowledge AI assistant in the CMA to answer questions about authenticating to the Client.
For other questions, please contact Support.