Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
Notice: | Welcome to the Digital UNIX Conference |
Moderator: | SMURF::DENHAM |
Created: | Thu Mar 16 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 10068 |
Total number of notes: | 35879 |
UNIX V4.0a ---------- I am having problems with C2 and the CDE Account Manager when creating new accounts that have the ""Force Password Change at Next Logon"" set i.e. a tick in the box. If I create a new account then when the user logs on for the first time they are not forced to change their password. The project that I am working on has a requirement that the user should change their password on first logon. The extracted record using edauth is as follows:- test5:u_name=test5:u_id#206:u_pwd=.........:u_succhg#842972757:\ u_pwdchanger=root:u_oldcrypt#0:u_lock@:chkent Anybody else seen this problem ?? Steven Wright
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
8884.1 | workaround | NETRIX::"[email protected]" | Ann Majeske | Wed Feb 19 1997 11:46 | 15 |
I don't know why your system is not properly setting the u_psw_change_reqd field. I tried this on a V4.0 system and it worked fine. I don't have a V4.0a system set up to test it. As a workaround, you can use /tcb/bin/edauth to add the u_psw_change_reqd field to the user's account information. The users account should look like: test5:u_name=test5:u_id#206:u_pwd=.........:u_succhg#842972757:\ u_pwdchanger=root:u_oldcrypt#0:u_psw_change_reqd:u_lock@:chkent You can also get the same effect by zeroing the u_succhg field: test5:u_name=test5:u_id#206:u_pwd=.........:u_succhg#0:\ u_pwdchanger=root:u_oldcrypt#0:u_lock@:chkent [Posted by WWW Notes gateway] | |||||
8884.2 | Default record had flag set | GEOFFN::WRIGHT | Thu Feb 20 1997 03:10 | 12 | |
It would appear that the problem I have is that I had set the flag on the default record. As the individual records are a delta of what is set for the individual user and the default record the flag for the specific user did not get set. I have cleared the flag on the default record and changed the instructions to explicitly set flag when creating the individual users. Steve Wright |