Sun Java System Access Manager 2005Q4 
Sample 
 
Main Page

Pluggable User Status Event Interface Sample : SampleAMAuthCallBack

This file explains how to compile , deploy and configure the Pluggable User Status Event Interface Sample.

PRODUCT_DIR setting on different Platforms:

  • Solaris Sparc/x86 : PRODUCT_DIR = <install_root>/SUNWam

  • Linux             : PRODUCT_DIR = <install_root>/sun/identity

Steps to compile the SampleAMAuthCallBack Sample program on Solaris Sparc/x86, Linux 

Follow the steps given below to compile the sample found under <PRODUCT_DIR>/samples/authentication/spi/statuschangedcallback .
 
  • Set the following environment variables. These variables will be used to run the gmake command. You can also set these variables in the Makefile. This Makefile is in <PRODUCT_DIR>/samples/authentication/spi/statuschangedcallback.
    • JAVA_HOME

    • Set this variable to your installation of JDK. The JDK should be version 1.3.1_06 or higher.
       
    • CLASSPATH

    • Set this variable to refer to am_services.jar which can be found in the <PRODUCT_DIR>/lib directory. (Note: Include jaas.jar in your classpath if you are using JDK version less than JDK1.4)
       
    • BASE_DIR

    • Set this variable to the directory where the Access Manager is installed.
       
    • BASE_CLASS_DIR

    • Set this variable to the directory where all the Sample compiled classes are located.
       
    • JAR_DIR

    • Set this variable to the directory where the JAR files of the Sample compiled classes will be created. 
  • Go to the <PRODUCT_DIR>/samples/authentication/spi/statuschangedcallback directory and run gmake. 
  • Steps to "deploy" the SampleAMAuthCallBack program

    • Copy SampleAMAuthCallBack.jar from JAR_DIR to <PRODUCT_DIR>/lib. 
    • Update Web Container configuration file "server.xml" to add SampleAMAuthCallBack.jar to the classpath. "server.xml" file for different web containers can be found at:

    •  WebServer   -  /<WS-home-dir>/https-<WS-instance-name>/config/
    •  AppServer - /<AS-home-dir>/domain/domain1/server1/config/
          For all other web containers consult their documentation. 

      • Restart web container. 
    • WebServer - /<WS-home-dir>/https-<WS-instance-name>/restart
    • Application Server - /<AS-install-dir>/<domains>/<domain name>/<server instance>/bin/restartserv  (eg. /<AS-home-dir>/domains/domain1/server1/bin/restartserv)
    • For all other web containers consult their documentation. 

    Steps to configure the Pluggable User Status Event Interface :

          The Pluggable User Status Event Interface Sample can be configured at the Organization level. 
           Configuring AMAuthCallBack Sample for Organization :
    • Log in to Access Manager console as amAdmin to http://<host>.<domain>:<port>/<Service-Deploy-URI>/UI/Login
    • Select the "Access Control" tab.
    • Select the realm. 
    • Click on "Authentication" tab. 
    • Click on "Advanced Properties". 
    • Add "com.iplanet.am.samples.authentication.spi.statuschangedcallback.SampleAMAuthCallBack" to "Pluggable User Status Event Classes" attribute 
    • Click on "Save" to save the changes. 
    • Log out 
    • Enter URL http://<host>.<domain>:<port>/<Service-Deploy-URI>/UI/Login(If you choose to use an organization other than the default, please specify that in the URL using the 'org' parameter.) 
    • Debug information will be available in the AuthCallBackSample debug file next time someone is locked out or changes password via the LDAP module password change feature (and the debug level is set to message).

    On Windows2000

    Steps to compile the SampleAMAuthCallBack program on Windows2000

      • Go to the <install-root>\samples\authentication\spi\statuschangedcallback directory and run make. 

    Steps to deploy the ISAuthPostProcessSample Sample program

    • Copy SampleAMAuthCallBack.jar from JAR_DIR to <install-root>\lib
    • Update classpath with  SampleAMAuthCallBack.jar  in the Web Container  from which this sample has to run.
    • Restart Access Manager ("<install-root>\bin\amserver start). 

    Steps to configure the Pluggable User Status Event Interface :

    This sample can be can be set in the Core Auth Service for Organization. 

    Refer to this in the "Solaris"  section in this document.