Server Error for non-base 64 character, padded characters, or an illegal character among the padding characters occurs for specific users

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All


    Upon logging into a realm, specific users land upon a server error:


    Error log:

    Message="Error Message: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.



    Considering specific users may land upon this error, they may have certain characters in their attributes that fall out of the scope of what is considered to be Base64.

    • Base64 characters should exist within the following:
    A-Z, a-z, and 0-9

    • If there are more than two padded characters, you would see a value in a user's attribute, such as:

    Note that spaces do count as padded characters.

    • Illegal characters may exist in a user's name, such as:



    Check the user's attributes to see if there are any padded and/or foreign characters. More often than not, the issue will be tied to a foreign character in a user's name attribute.



    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.