Authentication and Authorization APIs › Configuration of All Custom Classes

Configuration of All Custom Classes

The following configuration information applies to all custom authentication schemes and active expressions implemented with the Java Authentication API and Java Authorization API:

• The library name is always smjavaapi.
• In the parameter field, the first item must be the name of the custom class you implemented with the Authentication API or Authorization API, as follows:
  • With authentication schemes, specify the name of the class you implemented from the base interface SmAuthScheme. The class name should include the fully qualified package name, such as:

    com.myorg.sdk.myclass

  • With active policies, active rules, and active responses, specify the name of the class you implemented from the base interface ActiveExpression.
• If any parameters are specified in the parameter field after the class name, the class name is separated from the parameters list by a space character.

  When SiteMinder calls the methods in an instance of your custom class, it passes the specified parameters. The class name is not passed. The parameters are passed as a single string. If the string contains multiple parameters, the parameters can be delimited in any way that the custom class requires.

• The class file specified in the parameter field must be referenced in the classpath directive of the JVMOptions.txt configuration file. This file is located in Netegrity/SiteMinder/Config within the SiteMinder installation path.
• With active expressions, the function name (that is, the entry point for the smjavaapi library file) is always JavaActiveExpression.