We are running an AS/400 in S/36E at security level 20. Securing our system had become a necessity and going to level 30 seemed like a big step for our small shop. When we discovered that procedures could not be secured because they are not objects, we decided to create our own security.
The first step was to change each user profile to LMTCPB(*YES). None of our user menus give them access to system menus so they are limited to what we give them.
We then created a physical file named USERAUTH to hold the procedure name and the user authorized to use it. The key to the file is procedure and user name. See the DDS in 1a. Each user that needs access to the procedure will have to be entered. We created a DFU program to modify the file and a CL program to start the DFU.
We then created a physical file named USERAUTH to hold the procedure name and the user authorized to use it. The key to the file is procedure and user name. See the DDS in Figure 1a. Each user that needs access to the procedure will have to be entered. We created a DFU program to modify the file and a CL program to start the DFU.
In each procedure called by a user menu, we execute a procedure named CHECKUSR at line 1, which is listed in 1b. CHECKUSR puts the procedure and user name in the LDA , then calls an RPG program named CHECKUSR, shown in 1c. The RPG program uses the procedure and user name as the key to the file USERAUTH. If that record does not exist, the user is not authorized to use the procedure and the LDA values are blanked out. The RPG program ends and the procedure CHECKUSR checks the LDA for blanks. When blanks are found, a message is sent to QSYSOPR, the job log is printed, the user is informed and the procedure is canceled.
In each procedure called by a user menu, we execute a procedure named CHECKUSR at line 1, which is listed in Figure 1b. CHECKUSR puts the procedure and user name in the LDA , then calls an RPG program named CHECKUSR, shown in Figure 1c. The RPG program uses the procedure and user name as the key to the file USERAUTH. If that record does not exist, the user is not authorized to use the procedure and the LDA values are blanked out. The RPG program ends and the procedure CHECKUSR checks the LDA for blanks. When blanks are found, a message is sent to QSYSOPR, the job log is printed, the user is informed and the procedure is canceled.
This procedure assumes that if a user is authorized to the menu option, the user is also authorized to any files that are used by that option.
- Brad Hooley
Editor's Note: This technique can be used on a S/36 very easily by simply building the USERAUTH file as indexed with a key length of 20 and starting on position 1. The procedure needs a LOAD/RUN OCL pair instead of the CALL statement; the SNDMSG command must be changed to MSG (leaving the first parameter blank), and the OCL statement that executes the DSPJOBLOG command can be removed altogether. Finally, the RPG program should have an F-spec with "F" on column 19, record length 20, key length 20, key location 1, followed by the I-specs necessary to describe the record (two fields only), and the KLIST/KFLD can be changed to MOVEL/MOVE to move the components of the key into field KEY.
TechTalk: Securing Procedures in S/36E
Figure 1A Physical file USERAUTH
A UNIQUE A R USER01 TEXT('USERS/PROCEDURES') A PROC 8A TEXT('PROCEDURE NAME') A USER 10A TEXT('USER NAME') A K PROC A K USER
TechTalk: Securing Procedures in S/36E
Figure 1B Procedure CHECKUSR
Figure 1b: Procedure CHECKUSR * PROCEDURE: CHECKUSR // LOCAL OFFSET-1,BLANK-18,DATA-'?PROC?' // LOCAL OFFSET-9,DATA-'?USER?' * // CALL CHECKUSR * // IFF '?L'1,18'?'= GOTO OK // SNDMSG MSG('?USER? TRIED TO ACCESS PROCEDURE ?PROC?. + UNAUTHORIZED!!!') TOUSR(QSYSOPR) // DSPJOBLOG OUTPUT(*PRINT) // PAUSE 'YOU ARE NOT AUTHORIZED TO USE THIS PROCEDURE!!!' // CANCEL // TAG OK
TechTalk: Securing Procedures in S/36E
Figure 1C RPG program CHECKUSR
FUSERAUTHIF E K DISK I UDS I 1 8 PROC I 11 18 USER C KEY KLIST C KFLD PROC C KFLD USER C KEY CHAINUSERAUTH 99 C 99 MOVE *BLANKS PROC C 99 MOVE *BLANKS USER C SETON LR
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online