The Forgot Password Web Service exposes a small set of actions from the Password Management system. The service allows remote clients to retrieve information about the forgot password configuration. In addition, it allows clients to retrieve information about the forgot password settings for a particular user, and perform challenge response and change password operations for a user.
The Forgot Password Web Service does not support the full range of password self-service operations. The Forgot Password Web Service is only for forgot password operations. If you want to create a custom user interface for performing password self service functions, such as answering or updating the user’s hint or answer, or updating the challenge response questions, or checking on the password policy status, you need to use the REST endpoints that have been added to RBPM.
Calls to the Forgot Password Web Service require HTTP authentication.
You can access the Forgot Password Web Service endpoint using a URL similar to the following:
http://server:port/warcontext/pwdmgt/service
For example, if your server is named “myserver”, your identity applications is listening on port 8080, and your User Application war file is named “IDMPROV”, the URL would be:
http://myserver:8080/IDMPROV/pwdmgmt/service
NOTE:The URL for the Forgot Password Web Service can be changed on the Forgot Password Settings page on the Administration tab in the identity applications. To change the URL, enter the new URL in the Forgot Password Web Service URL field at the bottom of the page.
You can access the WSDL for the Forgot Password Web Service using a URL similar to the following:
http://server:port/warcontext/pwdmgt/service?wsdl
For example, if your server is named “myserver”, your identity applications is listening on port 8080, and your User Application war file is named “IDMPROV”, the URL would be:
http://myserver:8080/IDMPROV/pwdmgt/service?wsdl
Before using the Web Service, you need to use the WSSDK tool or another SOAP tool kit to generate the stub classes. To allow your code to find the stub classes, you also need to add the JAR that contains the stub classes to your classpath.
If you want to use the NetIQ WSSDK tool, you can generate the client stubs by extracting the WSDL and running the wsdl2java utility. For example, you could run this command to generate the stubs in a package called com.novell.soa.af.pwdmgt.soap.impl:
"C:\Program Files\Java\jdk1.6.0_31\bin\java" -cp "../lib/wssdk.jar;../lib/jaxrpc-api.jar";"../lib/mail.jar";"../lib/activation.jar";"c:\Program Files\Java\jdk1.6.0_31\lib\tools.jar"; com.novell.soa.ws.impl.tools.wsdl2java.Main -verbose -ds gensrc -d C:\ -noskel -notie -genclient -keep -package com.novell.soa.af.pwdmgt.soap.impl -javadoc pwdmgt.wsdl
You can change the wsdl2java parameters to suit your requirements.