Making "Admin" Security Configuration Production-Ready

Replace the default PreConfiguredUserLoginModule with new production-ready providers.

Note: Please note these restrictions before beginning:

For LDAPLoginModule, special characters (for example, , = : ' " * ? &) cannot be used in the user name defined with the Authentication Filter property. This same property also does not support Chinese or Japanese characters in the user name and password properties.
For PreConfiguredUserLoginModule, the User Name property also cannot contain the same special characters (that is, , = : ' " * ? &).

Adding a Production-Grade Provider
Modify the "admin" security configuration to add a production-grade provider, typically an LDAPLoginModule. Most companies use an LDAP directory to maintain internal user accounts. This module integrates with most LDAP servers including Active Directory.
Mapping Unwired Platform Logical Roles to Physical Roles
Unwired Platform requires that you map these default platform roles: SUP Administrator and SUP Domain Administrator. In a development environment, these mappings are automatic if the provider roles use the exact logical role names. If the development environment roles do not match, then you must manually map them.
Encrypting a Sensitive Property in CSI.PROPERTIES
Generate an encrypted string to use as the sensitive property value in the csi.properties configuration file.

Parent topic: Enabling Authentication and RBAC for Administrator Logins

Previous topic: Logging Into Sybase Control Center with an Installer-Defined Password

Next topic: Disabling Authentication Caching and Increasing Log Levels