[Try this procedure in a test environment, before applying it on a production environment]
Sun Java ES Access Manager(here on referred as Access Manager or AM) supports most of the industry standard authentication mechanisms including
Access Manager provides an adminsitartive console to perform these configuration steps, the same thing can be achieved by using the command line interface tool called amadmin. if you are trying to set up Access Manager configuration for a farm of servers with different configuration directory then your best bet is to use the CLI tool for repeatability of the tasks. Moreover using this tool will be less error prone.
I have provided couple of XML templates to create each authentication instance. These XML templates has certain tagged variables that are required to be repalced with proper values that are specific to your deployment.
for example in the LDAP auth isntance template you need to replace the following tags
LDAP_SERVER:LDAP_PORT to some thing like ldapserver.example.com:389 USER_BASE_DN ==> dc=example,dc=com AM_LDAP_USER ==> a valid DN that has search permission to the user entries AM_LDAP_USER_PASSWD ==> passwd for the above user in plain text LDAPS_TRUE ==> true if you are using ldaps otherwise false
you can download and customize the remaining templates based on your requirements
AddADAuthInstance.xml AddAnonymousAuthInstance.xml AddAuthHTTPBasic.xml AddAuthJDBC.xml AddAuthMembership.xml AddAuthMSISDN.xml AddAuthNT.xml AddAuthRadius.xml AddAuthSafeWord.xml AddAuthSecurID.xml AddAuthUnix.xml AddAuthWindowsDesktopSSO.xml AddLDAPAuthInstance.xml
you got to be using
amadmin -u amadmin -w passwd -t template-xml-file