To change the options of a login module or to remove a standard login module, you use the authentication configuration functions of the SAP NetWeaver Administrator.
To add or update a custom login module, you use the Deploy view of the SAP NetWeaver Developer Studio.
To remove a custom login module, you use the Undeploy view of the Developer Studio.
If you change the options of a login module in the user store, the changes will be inherited by all policy configurations that use this login module.
If you change the options of a login module in a single policy configuration, the change applies only to that policy configuration. In this case, the login module no longer inherits its options from the user store. To restore the inheritance, change the options in the policy configuration or in the user store so that they are identical.
If you are deploying a Web application you can set it to automatically inherit the options of a login module in the user store. To do this, enter the login module's display name in the Web deployment descriptor's tag <login-module-name>, for example: BasicPasswordLoginModule. In this case the system ignores the options you configure in the Web deployment descriptor. If you want to configure specific login module options for a Web application, enter the class name of the login module, for example: com.sap.engine.services.userstore.jaas.BasicPasswordLoginModule. In this case the system ignores the options in the user store and uses the options you specify in the deployment descriptor.
More information about the Web deployment descriptor: web-j2ee-engine.xsd.
The type of the project in the SAP NetWeaver Developer Studio must be an Enterprise Application Project so that you can export a deployable file with an extension .ear. The Enterprise Archive (EAR) file must contain the following two files:
To check the connection, from the menu path choose SAP AS Java. Adjust the parameters if necessary, for example: in the field Instance host enter localhost, in the field Instance number enter 0 and then choose Register SAP Instance.
and chooseThe deployable file must contain a JAR file with the class of the login module and a configuration XML file with the name LoginModuleConfiguration.xml. The configuration file contains the display name, the class name and the options of the login module and is used by the system to automatically register the login module on the AS Java.
Note the following:
More information: Creating the Configuration File for Login Modules.
Before removing a login module, make sure that you have removed that login module from all policy configurations that use it. Otherwise those policy configurations will not work properly after the login module is removed.
To remove a login module (for example: BasicPasswordLoginModule), proceed as follows:
To remove a custom login module, you use the Undeploy view of the Developer Studio:
To check the connection, from the menu path choose SAP AS Java. Adjust the parameters if necessary, for example: in the field Instance host enter localhost, in the field Instance number enter 0 and then choose Register SAP Instance.
and chooseAll login modules that have the same class name as the undeployed module will also be removed.