About HP DCE/9000 Version 1.7
HP Password Management Server
Certain files that contain proprietary SecureWare algorithms have been omitted, but stubs are supplied that allow the resulting server to build. Note that certain values of the pwd_SecureWare_chk ERA (specifically, values 1 and 2) are unsupported, and will result in failures to pass strength checking if you attempt to use the example server as described in the documentation. The logfile entry will report that the pwd_SecureWare_chk level is not supported.
Build Process
The source code directory for pwd_mgmt and the files in it are installed write protected. To build this application, copy the files into a private, writable directory you create. This way the original files will continue to be available for you or others to consult.
cd to the private, writable directory where you copied the source files and type:
make
Your system’s /bin/make command should successfully build the client and server programs using the Makefile provided, if modified as above.
Unlike the other sample applications, where you are encouraged to generate a new UUID when you make modifications, you must not make changes to rsec_pwd_mgmt.idl. secd is linked with the client stub for the rsec_pwd_mgmt interface so changing the interface UUID will cause communication problems between secd and your Password Management Server.
Administrative Setup
The dce_config and pwd_config files supplied with this DCE release are set up to configure and start up a Password Management Server that conforms to the guidelines listed above.
In order to have the policies implemented by any Password Management Server apply to a given principal, the administrator must attach instances of the following two Extended Registry Attributes to the principal’s node in the DCE Registry:
pwd_val_type
The pwd_val_type attribute controls the type of password management that applies to a given principal. The values are:
Planning and Configuring HP DCE 1.7 |