Supported Username Variations

The following username variations are supported.

• user – A regular username is used.
• user@example.com – An email address is used as the username. For example, user@foo.bar.
• user@sc – A regular username is used and the security configuration is overridden by a username suffix.
• user@example.com@sc – An email address is used as the username and the security configuration is overridden by a username suffix. For example, user@foo.bar@sc.

For those usernames that override the security configuration, both the default security configuration associated with the domain as well as the security configuration specified in the X-SUP-SC request header are overridden. You must associate the specified security configuration with the domain to allow a successful connection, otherwise a 403 error is returned to the HTTP client. If a request refers to a non- existent domain or security configuration, a 404 error is returned. If you use mutual X.509 authentication with certificates, you can only override the domain default security configuration using request headers. If the specified security configuration does not exist, a 404 error is returned.