Pluggable Authentication Modules (PAMs)

Running Business Processes and Composite Applications 10.4 | Running Business Processes and Composite Applications | webMethods Integration Server Administrator’s Guide | Customizing Authentication Using JAAS | Pluggable Authentication Modules (PAMs)

Implementing JAAS custom login modules supersedes the pluggable authentication module (PAM) approach to customizing authentication used in previous versions of Integration Server. Beginning with Integration Server version 8.0, customizing authentication with PAMs is deprecated.

PAMs will continue to work in Integration Server version 8.0 and later as an extension to the JAAS login modules BasicLoginModule and X509LoginModule:

If you registered a PAM for the "basic" authentication mechanism, it will be treated as an extension to BasicLoginModule.

If you registered a PAM for the "X509" authentication mechanism, it will be treated as an extension to X509LoginModule.

If a PAM is registered and the corresponding JAAS login module (BasicLoginModule or X509LoginModule) is called, authentication is first attempted on the credentials supplied for that module. If that authentication is not successful, then the PAM is called and another attempt to authenticate the user is made.

Important: Removing the line of code specifying the BasicLoginModule or X509LoginModule in the JAAS configuration file will disable any registered PAM for the corresponding authentication mechanism.

Note: Information about customizing Integration Server client authentication with PAMs, is available in webMethods Integration Server Administrator’s Guide version 8.0.