Password expiry management for HTTP basic authentication
When basic authentication is used for an HTTP connection, CICS® web support checks the user ID and password in the external security manager. If the password has expired, the CICS-supplied utility program DFHWBPW is used to prompt the user to select a new password. You can customize or replace the pages presented to the user by DFHWBPW.
DFHWBPW is used only for password expiry management when the TCPIPSERVICE definition that applies to the request is defined with the BASIC, AUTOREGISTER, or AUTOMATIC option for the AUTHENTICATE attribute. Although DFHWBPW has a structure similar to a converter program, it is not part of the normal CICS web support processing path, so you do not need to add code to it for any other purpose. When the user has selected a new password, DFHWBPW restarts the request submission by redirecting the client to the URL for the original request, so that the complete processing path for the request occurs as normal.
- Password prompt page. This page contains two elements:
- A message about password validity. The initial message displayed to the user states that the password has expired. A user ID can have both a standard password and a password phrase. Passwords between 9 and 100 characters in length are password phrases; passwords of 8 characters or less are standard passwords. Standard passwords and password phrases operate independently of each other. If a standard password has expired, it must be replaced with a new standard password. Similarly, if a password phrase has expired, it must be replaced with a new password phrase. If the user's attempt to change the password fails (for example, the two supplied copies of the new password do not match), further messages are displayed to explain the problem.
- An HTML form for the user to change the password.
- Confirmation and request refresh page. This page confirms that the expired password has been successfully replaced, and provides a refresh tag and URL link so that the request can be remade automatically or manually.
The content and function of each of the DFHWBPW templates is as follows:
- DFHWBPW1
- Part of the password prompt page. Provides the HTML page heading
for the page, and sets symbols for the possible password validity
messages (using the server-side include technique for setting symbols).
The messages provide the following information:
- message.1
- Password has expired.
- message.2
- The entered user ID is invalid.
- message.3
- The two copies of the proposed new password do not match.
- message.4
- The previous password entered (the one that has just expired) is not correct.
- message.5
- The proposed new password is not permitted by the external security manager, because of password quality rules.
- message.6
- The user ID is now revoked.
- DFHWBPW2
- Part of the password prompt page. Builds an HTML form where the user can input a user ID, the old (expired) password (or password phrase), and two identical copies of a proposed new password. You can customize DFHWBPW2 to change the text used to prompt the user, or otherwise change the layout of the page. However, you must not modify the contents of the form tag, or any of the input tags. If you do, DFHWBPW might not work as intended.
- DFHWBPW3
- Confirmation and request refresh page. The text notifies the user
that the expired password was successfully replaced, and explains
that the user will shortly be prompted by the client to enter the
password again. You can customize the text and layout of the page.
DFHWBPW3 restarts the request process. It contains a meta http-equiv="Refresh" tag that causes an automatic redirection after ten seconds to the page that the user had originally requested when the expired password was detected. You can change the time limit on this tag or remove it if you do not want users to be redirected automatically. However, the modified page must always contain a link forward to the originally requested page. The URL for that page is in the symbol &dfhwbpw_target_url; . Restarting the request process means that, if the web client has cached the old password, it can be replaced with the new password immediately, and also means that the CICS web support processing path is unaffected.