Day 2 - Session 1-3 - SMS
Day 2 - Session 1-3 - SMS
Day 2 - Session 1-3 - SMS
Day 2 – Session 1 - 3
Security Management System
Dates
22/02/2011 Tech Support Program
Venue
Microcred, Senagal
SMS in T24
SIGN ON NAME
• Name entered by the user to access T24 system
• Must be different from USER ID
• Must be unique
CLASSIFICATION
• Identifies whether the user is an employee of the bank or
• Customer of the bank
– INT - Bank employee
– EXT - Customer
COMPANY CODE
• Specifies the company codes for which the user has got access
PASSSWORD VALIDITY
• Specifies the Frequency and Date of password change
• Frequency setup is done based on the bank policy
• System will recycle the date automatically
START TIME
• Specifies the time from which the user can access T24 system
• It is possible to specify more than one period for a day
• If 1 or 2 digit value is entered, then system will take it as minutes
from midnight
END TIME
• Specifies the time till which the user can access T24 system
ATTEMPTS
• Number of unsuccessful attempts allowed during login
• After this count user profile will get disabled automatically
• Disabled user profiles can be identified by using the mainline
routine PASSWORD.EXCEPTION
INIT APPLICATION
• Applicationor Menu to be executed whenever the user logs on
to the system
• Menu should be prefixed with “ ? “
CUSTOMER
• Customer financial information that can be accessed by the
External user
• Mandatory for External User
• This field is enabled only for external users
ACCOUNT
• External user cannot access Account information If it is not
given in this field
• Cannot be entered unless CUSTOMER is entered
ATTEMPTS SINCE
• Number of unsuccessful attempt is updated
• If
this count is greater than the number in ATTEMPTS,
password will get disabled
APPLICATION LOG
• Specifies
whether a log should be written to PROTOCOL every
time when the user tries to access any T24 application
FUNCTION ID LOG
• Specifies
whether or not full details of every Application,
Function and record ID accessed by this User should be
recorded in the PROTOCOL file
CLEAR SCREEN
• Ifset to Yes, it clears the screen whenever the user finishes
processing
• If set to No, screen will remain in the same page after
transaction processing
PRINTER FOR RPTS
• Printer to be used for printing the reports
• Should be a valid printer or &HOLD&
AMOUNT FORMAT
• Specifies the separators to be used for formatting amounts
• It is a two character pair
• First is the amount separator , second is the decimal separator
– Ex : ,.
ATTRIBUTES
• COMMAND.LINE - User is allowed to use command line
• EXPLORER - Allows the user to use the Application explorers
• ENQUIRY.INDEX - Allows access to the enquiry index, where
the user is given access only to enquiries
• REALTIMEENQUIRY - Allows the use of real time enquiries for
this user
• LOCK.PREFERENCES - Prevents the user from gaining access
to various Desktop settings including file locations and some
system administrative functions
Company Restr
• Specifies the company to which the user is allowed to use the
application, version and function attached in the related field
• ALL – To allow access all companied in COMPANY CODE field
APPLICATION
• Valid T24 application allowed for the given company
• ALL.PG – Allowed for all applications and programs
• ALL.PG.H – Only ‘H’ type files can be accessed
• SMS ID is prefixed with @ symbol
VERSION
• Name of the version preceded by ,
•? and * can be used as wild card characters
•* - For any number of characters
•? – For single character
FUNCTION
• Specifies the allowed functions
• ALL – Will automatically update all the functions except ‘Q’
•N – No function allowed
PWD REPETITION
Number of different passwords a user can use before
repeating the first password
PASS NUMERIC
• Number of numeric characters must be entered in the password
PASS OTHER
• Ay character that must be part of the password
• Ex : $
USER PW ATTEMPT
• Value should be valid USER ID
• This will reset the password and number of attempts
USER ATTEMPT
• Value should be valid USER id
• This will reset the number of login attempts
• Count will start from 0 again
ID - Application name
• Ex : FUNDS.TRANSFER
Override text
• Allows
the user to define specific classifications for the override
messages of the ID application
• Should be the same as defined in Override application
Define Record Id from OVERRIDE.CLASS.DETAILS in field
‘Override Detail’
User Initiated
Inactive Session
Hardware Failure