Security Patrol: Security Questions & Answers

IBM i (OS/400, i5/OS)
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Q:I am trying to consolidate two AS/400 systems into a single, large AS/400 system. Some objects and user profiles exist on only one system, but some exist on both systems. What is the proper way to restore the user profiles and authority from the two systems?

A: With a user profile that has *ALLOBJ authority, perform a Save Security Data (SAVSECDTA) from both systems (SYSTEM_A and SYSTEM_B) to save the user profiles, authorization lists, and private authorities.

Restore a single system at a time with the commands shown in 1. Use a profile with *ALLOBJ and *SECADM authority. Be aware that the ALWOBJ-DIF parameter value of *ALL used by the commands in 1 will cause any existing object to be replaced if an object of the same name is found in the save data.

Restore a single system at a time with the commands shown in Figure 1. Use a profile with *ALLOBJ and *SECADM authority. Be aware that the ALWOBJ-DIF parameter value of *ALL used by the commands in Figure 1 will cause any existing object to be replaced if an object of the same name is found in the save data.

ALWOBJDIF(*ALL) should be specified on all restore operations to attach the objects to authorization lists because the restore system is different than the save system. If the owner of the objects on the system you're restoring to is different than the user profile restoring the objects, the objects will not be restored unless you specify ALWOBJDIF(*ALL).

The user profiles that exist on both systems A and B will have the attributes (password, initial program, special authority) from the system restored last. Profiles that exist on only one system won't have their attributes changed.

Special Authority: The user profiles with *ALLOBJ authority other than QSECOFR, QSYS, QLPAUTO, and QLPINSTALL will have *ALLOBJ authority revoked if the system is at security level 30 or higher. You will need to sign on as QSECOFR and grant *ALLOBJ authority to any profile that had *ALLOBJ authority.

Ownership: The owners of objects that exist on both systems will be the owner from the first system restored. Assuming system A is restored first, the ownership will be as shown in the table in 2.

Ownership: The owners of objects that exist on both systems will be the owner from the first system restored. Assuming system A is restored first, the ownership will be as shown in the table in Figure 2.

Public Authority: The *PUBLIC authority from the first system restored will be used because the object already exists when the second system restore occurs and the authority of an object on the system does not change. The column COMBINED_AB in the table in 3 shows the resulting authority after restoring both systems.

Public Authority: The *PUBLIC authority from the first system restored will be used because the object already exists when the second system restore occurs and the authority of an object on the system does not change. The column COMBINED_AB in the table in Figure 3 shows the resulting authority after restoring both systems.

Private Authority: The private authorities are additive. The table in 4 shows the users' authority to objects before and after the restore. However, an *EXCLUDE from the last system will remove any previous authorities. This is illustrated by user USERAB3 in the table.

Private Authority: The private authorities are additive. The table in Figure 4 shows the users' authority to objects before and after the restore. However, an *EXCLUDE from the last system will remove any previous authorities. This is illustrated by user USERAB3 in the table.


Security Patrol: Security Questions & Answers

Figure 1 Command to Restore Objects

 Using system A data: RSTUSRPRF DEV(xxx) USRPRF(*ALL) ALWOBJDIF(*ALL) RSTLIB specify ALWOBJDIF(*ALL) RSTDLO specify ALWOBJDIF(*ALL) RSTAUT Using system B data: RSTUSRPRF DEV(xxx) USRPRF(*ALL) ALWOBJDIF(*ALL) RSTLIB specify ALWOBJDIF(*ALL) RSTDLO specify ALWOBJDIF(*ALL) RSTAUT 
Security Patrol: Security Questions & Answers

Figure 2 Restored Object Ownership

 UNABLE TO REPRODUCE GRAPHICS 
Security Patrol: Security Questions & Answers

Figure 3 Restored Object Public Authority

 UNABLE TO REPRODUCE GRAPHICS 
Security Patrol: Security Questions & Answers

Figure 4 Restored Object Private Authority

 UNABLE TO REPRODUCE GRAPHICS 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  •  

  • LANSA 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.

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra 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: