Restrictions on Characters

1 General Consideration

Character restrictions imposed on each inbound field vary. cmd-auth OpenAPI documentation details character requirements.
You may note that the application imposes fewer restrictions on characters when compared with other frameworks.

There are no restrictions on the output (i.e. "Ӽĕîϰ₿"), but the content must be able to survive the transport to the final destination (see setting validation -> others -> global_character_encoding_upstream, validation -> others -> character_encoding_per_request and cmd-auth implementations).

3 Using Unicode Characters

In order to enable Unicode Characters (cyrillic, greek etc.) the setting validation -> others -> restrict_characters must be set to false. When this setting is set to false you will have to perform your own checks on fields. Restrictions regarding the length of field values are always in effect.

4 Handling Sensitive User Details

Restrictions imposed by default for sensitive user details may be disabled by setting application -> encrypted_content to true. The following user details are considered to be sensitive: email, password, username and phone number.
When application -> encrypted_content is set to true, it is assumed that all sensitive details are encrypted and no format checks will be performed. These details will be stored in the database as received from the upstream.
This mode may be useful when you do not trust the application fully, or when required by rules and regulations.