B - Production Support » Agrobank Support » IBAM

i need following:

1. CIF number
2. last login date and time

Abu Bakar, please get the necessry information requested from Moein since this is production issue which suppose to follow the production process. Besides, l guess this case should be refer to IBAM ID, if yes, you may want to get the user id.

Please refer attachment

User id = 3426

Issue: IBAM User ID that not login(inactive) to system for more than 30 days, not showing Dormant status. Earlier it display the Dormant status. Please refer to the attachment.

User ID: 3476
User Name: A1727
Last Login Date/Time: 31/7/2012 @ 4:56:40pm
Status Display as: Normal
Expected Status Display as: Dormant

since this is production issue, below are things to be done:

1. make sure the upass configuration of IBAM is set for user to be dormant more than 30 days, in uat is okey we tested and if dormant it shows.

you can try with this user in UAT (http://10.6.6.20:9081/ibam.uat/common/Login.do)
navitester
aaaa1111

2. try to get IBAM log file of the time and date user attempt, if you do not have log file get user to try and get the log file so that we can see what is happening.

Email to User on the resolution to check the upass configuration of IBAM is set for user to be dormant more than 30 days. Pending for customer feedback if any other issue occurred.

Request ID has been closed with no further issue from customer.

Please check the following settings to confirm before deployed to production.

PASSWORD_MAX_ERROR=2
#requested by agrobank audit (Azreen) to change the value on 27th March 2012
#PASSWORD_GENERAION=6
#PASSWORD_EXPIRY_DAY=60
PASSWORD_GENERAION=11
PASSWORD_EXPIRY_DAY=90
PASSWORD_MIN_LENGTH=8
PASSWORD_COMPLEXITY=1

# Suspend Root or Admin ID for max password error, in minute
SUPERVISOR_ID_SUSPEND=30

FYI, Agrobank IT team have compare the upass configuration of IBAM (upass.cfg)for development and production and found some differences from PASSWORD_MAX_ERROR to PASSWORD_COMPLEXITY as below:

Development

# NOTE:
# Make sure there is no tailing space at the parameter, eg "...=3" and not "...=3  " 
# Tailing space will cause "ERR: property Not Found" exception.
#
# log
LOG_LEVEL=0

# Password Expiry
# expiry=0 denotes no expiry date
# If the expiry_day change after operation, the users created/changed password before this
# parameter change will not take effect.
#
# Password Complexity set to 1 denotes the password must consists of:
# at least an upper case [A..Z] and at least a lower case [a..z] and at least a numeric [0..9] and
# at least a special character [!@#$%^&*()_+<>?]
#
PASSWORD_MAX_ERROR=2
#requested by agrobank audit (Azreen) to change the value on 27th March 2012
#PASSWORD_GENERAION=6
#PASSWORD_EXPIRY_DAY=60
PASSWORD_GENERAION=11
PASSWORD_EXPIRY_DAY=90
PASSWORD_MIN_LENGTH=8
PASSWORD_COMPLEXITY=0

# Suspend Root or Admin ID for max password error, in minute
SUPERVISOR_ID_SUSPEND=30

#TAC timeout in Sec
#TAC_DEFAULT_TIMEOUT denotes validity of life span in second for TAC 
#TAC_LIFTSPAN_TIMEOUT denotes the validity of life span second after the 1st used
#TAC_REPEAT_TIMEOUT denotes the time in second allowed for next TAC generation
TAC_LIFTSPAN_TIMEOUT=3600
TAC_DEFAULT_TIMEOUT=3600
TAC_MAX_ERROR=3
TAC_REPEAT_TIMEOUT=3600
# 20090420 incorp max used of TAC
TAC_MAX_USE=999

# Database Connection Info for testing
#DB_DRIVER=oracle.jdbc.driver.OracleDriver
DB_DRIVER=com.microsoft.sqlserver.jdbc.SQLServerDriver
#DB_URL=jdbc:oracle:thin:@219.95.244.227:1521:IBSDEMO
DB_URL=jdbc:sqlserver://10.6.6.21:1433;databaseName=agroib_db.uat
DB_USERNAME=agroib_db.uat
DB_PASSWORD=P@$$w0rd

# Database Connection info for JNDI
# org.jboss.resource.adapter.jdbc.jdk5.WrappedConnectionJDK5@bb2f6e
DB_USE_JNDI=Y
DB_DATASRC_REF=jdbc/UatDatasource

Production

# NOTE:
# Make sure there is no tailing space at the parameter, eg "...=3" and not "...=3  " 
# Tailing space will cause "ERR: property Not Found" exception.
#
# log
LOG_LEVEL=0

# Password Expiry
# expiry=0 denotes no expiry date
# If the expiry_day change after operation, the users created/changed password before this
# parameter change will not take effect.
#
# Password Complexity set to 1 denotes the password must consists of:
# at least an upper case [A..Z] and at least a lower case [a..z] and at least a numeric [0..9] and
# at least a special character [!@#$%^&*()_+<>?]
#
PASSWORD_MAX_ERROR=3
PASSWORD_GENERAION=6
PASSWORD_EXPIRY_DAY=0
PASSWORD_MIN_LENGTH=4
PASSWORD_COMPLEXITY=0

# Suspend Root or Admin ID for max password error, in minute
SUPERVISOR_ID_SUSPEND=30

#TAC timeout in Sec
#TAC_DEFAULT_TIMEOUT denotes validity of life span in second for TAC 
#TAC_LIFTSPAN_TIMEOUT denotes the validity of life span second after the 1st used
#TAC_REPEAT_TIMEOUT denotes the time in second allowed for next TAC generation
TAC_LIFTSPAN_TIMEOUT=3600
TAC_DEFAULT_TIMEOUT=3600
TAC_MAX_ERROR=3
TAC_REPEAT_TIMEOUT=3600
# 20090420 incorp max used of TAC
TAC_MAX_USE=999

# Database Connection Info for testing
#DB_DRIVER=oracle.jdbc.driver.OracleDriver
DB_DRIVER=com.microsoft.sqlserver.jdbc.SQLServerDriver
#DB_URL=jdbc:oracle:thin:@219.95.244.227:1521:IBSDEMO
DB_URL=jdbc:sqlserver://172.16.51.12:1433;databaseName=agroib_db.prod
DB_USERNAME=<username>
DB_PASSWORD=<password>

# Database Connection info for JNDI
# org.jboss.resource.adapter.jdbc.jdk5.WrappedConnectionJDK5@bb2f6e
DB_USE_JNDI=Y
DB_DATASRC_REF=jdbc/ProdAgroDatasource

Please provide the correct setting and exact file to set for user to be dormant more than 30 days

dormant status the setting is under AppConfig.properties :

#Application check for maximum days before dormant
application.max.dormant.day=30

Hi Alwi,

Although the AppConfig file already updated as advised before, its still display the user status as 'Normal'

 
userid   username        name       status        update date             lastlogin date           creation date
  896    SNM5234    SITI NORAHAYU   Normal   13/08/2012 11:41:57 AM   06/12/2012 10:32:09 AM   13/01/2012 12:38:44 PM
                    BT MOHD DESA

Changes done :

#Application check for maximum days before dormant
application.max.dormant.day=30

User status is normal because the user haven't try to login.
when the user try to login Then the dormancy period will be checked and the status will be changed to dormant.

Kindly ask the user to try login,

Thanks,