You can choose to use a user authentication mechanism other than the built-in MobiLink mechanism. Reasons for using a custom user authentication mechanism include integration with existing DBMS user authentication schemes or external authentication mechanisms; or supplying custom features, such as minimum password length or password expiry, that do not exist in the built-in MobiLink mechanism.
There are three custom authentication tools:
mlsrv10 -zu+ option
The mlsrv10 -zu+ option allows you to control the automatic addition of users. For example, specify -zu+ to have all unrecognized MobiLink user names added to the ml_user table when they first synchronize. The -zu+ option is only needed for built-in MobiLink authentication.
The authenticate_user script and authenticate_parameters script both override the default MobiLink user authentication mechanism. Any user that successfully authenticates is automatically added to the ml_user table
There are several predefined scripts for the authenticate_user event that are installed with MobiLink. These make it easier for you to authenticate using LDAP, POP3, and IMAP servers. See Authenticating to external servers.
Use authenticate_user to create custom authentication of user IDs and passwords. If this script exists, it is executed instead of the built-in password comparison. The script must return error codes to indicate the success or failure of the authentication.
Use authenticate_parameters to create custom authentication that depends on values other than user IDs and passwords.
Java and .NET user authentication
SQL user authentication
Authenticating to external servers