IBM i Global

IBM i 

A space for professionals working with IBM’s integrated OS for Power systems to exchange ideas, ask questions, and share expertise on topics like RPG and COBOL development, application modernization, open source integration, system administration, and business continuity.


#Power


#IBMi
#Power
 View Only

RE: Unable to logon after OS restore before IPL options 

05/03/24 02:28 AM

Comments

01/15/26 09:43 AM

Security Levels (QSECURITY system value):
Level 10: No security
Level 20: Password security (default after restore)
Level 30: Resource security
Level 40: Enhanced integrity protection
Level 50: Maximum security + integrity

Restore Process Flow:
[Backup Media] → [LIC Restoration] → [OS Objects Restored]
                                    ↓
                            [QSECURITY = ?]
                            [User Profiles = Restored State]
                            [System Values = Backup Values]
                                    ↓
                            [IPL Options NOT Applied]
                                    ↓
                        [Security Mismatch = LOGON DENIED]

L(success) = f(QSECURITY, QMAXSIGN, QPWDEXPITV, QRETSVRSEC, QALWOBJRST)

Where logon succeeds if:
1. QSECURITY ≥ 20 AND User_Password_Valid = TRUE
2. QMAXSIGN violations < threshold
3. Password_Expiration_Date > Current_Date
4. User_Profile_Status = *ENABLED

Normal IPL Path (Without Options):
Power On → Load LIC → Initialize OS → 
→ Apply DEFAULT System Values → 
→ Enforce CURRENT Security → 
→ User Logon (FAILS if mismatch)

IPL with Manual/DST Options:
Power On → Enter IPL Options Menu →
→ Override System Values (Option 3) →
→ Bypass Security (QSECURITY=10 temporary) →
→ Allow QSECOFR logon →
→ Fix security configuration →
→ Normal IPL

P(failure) = 1 - ∏(i=1 to n) P(condition_i satisfied)

Where conditions include:
P(C₁) = P(QSECURITY compatible)     ≈ 0.60
P(C₂) = P(Password not expired)     ≈ 0.40
P(C₃) = P(User profile enabled)     ≈ 0.85
P(C₄) = P(Authorities restored)     ≈ 0.50
P(C₅) = P(QMAXSIGN not violated)    ≈ 0.70

P(success) = 0.60 × 0.40 × 0.85 × 0.50 × 0.70
P(success) ≈ 0.0714 (7.14%)

Therefore:
P(failure) = 1 - 0.0714 = 92.86%

User Profile States After Restore:

[RESTORED]
    ↓
[Password Hash Mismatch?] ────YES───→ [AUTH FAILURE]
    ↓ NO
[QMAXSIGN Lockout?] ───────YES───→ [PROFILE DISABLED]
    ↓ NO
[Authority Verification]
    ├─→ [Missing *ALLOBJ] ───→ [INSUFFICIENT AUTH]
    ├─→ [Missing Special Auth] → [LIMITED ACCESS]
    └─→ [All Checks Pass] ────→ [LOGON SUCCESS]
                                    ↑
                                [Rare ≈7%]

Password Storage Formats:
- DES Hash (Legacy, pre-V5R3)
- SHA-1 Hash (V5R3+)
- SHA-512 Hash (V7R1+)

Hash Verification Formula:
H(input) = SHA-512(password || salt || system_id)

Failure occurs when:
- Backup from V6R1, Restore to V7R4
- Hash algorithm mismatch
- Salt regeneration on new system
- System ID changed (different machine)

Verification: H(user_input) ≟ H(stored)
If system_id changed: H(user_input) ≠ H(stored) → AUTH FAIL

DST IPL Options (Mode: Manual):

1. Install System Licensed Internal Code
2. Work with Disk Units
3. Define or Change System at IPL ←── CRITICAL
4. Use Dedicated Service Tools (DST)
5. Save Licensed Internal Code
6. Display/Alter IPL Parameters

Option 3 Submenu:
├── System Value Commands
│   ├── QSECURITY (Set to 10 temporarily)
│   ├── QMAXSIGN (Disable lockout)
│   └── QPWDEXPITV (Disable expiration)
├── IPL Attributes
│   └── Secure Mode Override
└── Apply Changes and Continue IPL

Statistics
0 Favorited
31 Views
1 Files
0 Shares
1 Downloads
Attachment(s)
pdf file
Cloud_Optical_Repository.pdf   884 KB   1 version
Uploaded - 05/03/24