Differences between cwbCO_Signon and cwbCO_VerifyUserIDPassword

Following are listed some of the significant differences between the cwbCO_Signon and cwbCO_VerifyUserIDPassword commands..

  • cwbCO_VerifyUserIDPassword requires that a user ID and password be passed-in (system object values for these will NOT be used), and will not prompt for this information. cwbCO_Signon may use prompting, depending on other system object settings, and in that case will use whatever values are supplied by the user for user ID and password in its validation attempt.
  • Since cwbCO_VerifyUserIDPassword never will prompt for user ID and password, these settings in the specified system object will not be changed as a result of that call. A call to cwbCO_Signon, however, may change the user ID or password of the system object as the result of possible prompting for this information.
  • cwbCO_VerifyUserIDPassword ALWAYS will result in an IBM i connection being established to perform user ID and password validation, and to retrieve current values (such as date and time of last successful signon) related to signon attempts. cwbCO_Signon, however, might not connect to validate the user ID and password, but instead may use recent results of a previous validation. This is affected by recency of previous validation results as well as by the Validation Mode attribute of the given system object.
  • The password is cached in the IBM i password cache only in the case of the successful completion of cwbCO_Signon, never as the result of a call to cwbCO_VerifyUserIDPassword.
  • cwbCO_VerifyUserIDPassword NEVER will set the system object state to 'signed on', whereas a successful cwbCO_Signon WILL change the state to 'signed on'. This is important because when a system object is in a 'signed on' state, most of its attributes may no longer be changed.