El nexo entre tecnología y negocios
 
[ AHT00116 ] Enable a user blocked from the data base
Summary
When a user is blocked due to several vain attempts to enter a mistaken password and Apia cannot be acceded to unblock him, he can be unblocked from the data base in which it is being working.

It is applied to
  • Apia ALL.ALL.ALL


Procedure

Apia's table: USERS must be selected. The following columns must be modified for the row corresponding to the blocked user:

  • usr_block_desc: it must have the text “null”.
  • usr_login_count: it must have 0.
  • usr_flags: there is a code of 4 digits for this column.

Each one of these corresponds to a Boolean value (0, 1) which makes reference to a user's property. The position which must be modified is 4, in which “xxx0”must be collocated, being “x” the current value for those positions, modifying in that way only the last position.

Position  0, indicates if the user is hidden, for instance, busClass user has the flag in 1.

Position 1, indicates if the user is disabled. 

Position 2, indicates if the user is global. 

Position 3, indicates if user's password has expired. 

Position 4, indicates if user's password never expires. 



Related from
[ AFC00105 ] User Object of the API
[ ANF00181 ] Eliminate user from the API
Suggested items
[ ATI00202 ] Datasheet "Automatic Password Reset"
[ ATI00201 ] Datasheet "Password Reset Administration"
[ ANF00136 ] Strong password politics
[ ANF00220 ] Login screen customization
[ AFC00147 ] Some methods have been incorporated to be able to assign licences, block and unblock documents of an entity
[ ABR00013 ] User.unLock is not unlocking the user
[ ANF01553 ] Chat broadcast messages monitoring
[ AFC00124 ] Repetitions control in user's password.
[ AFC00106 ] Set the user's password expiration from API
[ AFC00394 ] Automatic password reset