Setting Up the Admin Security Configuration

Configure the admin security configuration to authenticate all administrator users. In a development environment, the admin security configuration points to the OpenDS LDAP server and the default role mapping. To secure your Unwired Server infrastructure in the development environment, you must use Sybase Control Center to set the admin security configuration to point to your security repository server and configure the appropriate role mapping.

1. Open Sybase Control Center.
2. In the left navigation pane, expand the Security folder.
3. Select Admin.
4. In the right administration pane, configure authentication and authorization by clicking the corresponding tab, and configuring properties of the providers you add as required.
   By default, authentication and authorization uses No Security. You can customize the security configuration by removing this provider and other types of providers.
5. Configure the same LDAP login provider that is used to authenticate and authorize Sybase Control Center administrative users. You can use a single provider can be used for both Sybase Control Center and Unwired Platform administrators.
   1. Click New.
   2. Select the provider.
   3. Set the controlFlag property to sufficient. Then ensure that all property values that are suitable for your security requirements.
   4. Set this provider to come before the NoSecLoginModule.
      Note: Do not delete this module yet. Otherwise, if you have misconfigured the new login module, you may have issues logging in to Sybase Control Center to correct the issue.
   5. Click OK, to save the configuration locally.
6. Ensure the login has, and ordered before the NoSecLoginModule on the list.
7. Click Save to save the security configuration changes.
8. Test the security before removing the NoSecLoginModule from the security configuration.
   1. Set security logging to a DEBUG value.
   2. Logout of Sybase Control Center and login with a user ID from the new security backend who should have SUP Administrator role.
   3. Check the server log to see if the new login module authenticated the user successfully. If not, modify the login provider properties until you can login successfully.
   4. Once the new login module is working correctly, remove the NoSecLoginModule providers and save the configuration.
   5. Set security logging to INFO, or something more appropriate.