Hello list,

The subject line states my problem in a nutshell.  I'm trying to do a 
direct-to-z/os download of maintenance from ShopZ.  I noticed the hash in the 
SERVER section on the package that ShopZ gave me is all zeros.  I've always 
just used the "javatruststore" for my downloadkeyring in the CLIENT section and 
this time it's saying I need a signaturekeyring.  I plugged the CERTAUTH info 
into the signaturekeyring section and now I'm getting a GIM69271S error.  

Here's my CLIENT info.

<CLIENT                           
javahome="/java_home_dir"         
downloadmethod="https"            
downloadkeyring="javatruststore"  
signaturekeyring="*AUTH*/*">      
</CLIENT>                         

Here's the error I'm getting.

GIM69271S ** SIGNATURE VALIDATION FAILED BECAUSE THE SIGNING CERTIFICATE IS NOT 
    
             TRUSTED. THE GIMZIP PACKAGE WAS SIGNED BY A CERTIFICATE WITH       
    
             SUBJECT NAME                                                       
    
             "CN=IBM EF Package Signing-G1, OU=IBM Code Signing, O=IBM 
Corporati    
             on, C=US", SERIAL NUMBER "16" AND SHA256 FINGERPRINT               
    
             
"0299dc5ab3f2d2beb5b8ac999a8b49969bea9b3f964756a7d94213a475c38c10".    
             THE SIGNING CERTIFICATE WAS ISSUED BY "CN=STG Code Signing CA - 
G2,    

If I look in RACF at the certificate I see this:

Label:STG Code Signing CA - G2                                          
Certificate ID:###############################################         
Status:NOTRUST                                                          
Start Date:2013/05/31 23:00:00                                          
End Date:  2033/05/31 22:59:59                                          
Serial Number:00                                                        
                                                                        
Issuer's Name:CN=STG Code Signing CA - G2.OU=IBM Code Signing.O=IBM     
Corporation.C=US                                                        
                                                                        
Subject's Name:CN=STG Code Signing CA - G2.OU=IBM Code Signing.O=IBM    
Corporation.C=US                                                        
                                                                        
Signing Algorithm:sha256RSA                                              
Key Usage:CERTSIGN                                                       
Key Type:RSA                                                             
Key Size:2048                                                            
Private Key:NO                                                           
                                                                         
Certificate Fingerprint (SHA256):##:##:##:##........
Ring Associations:                                                       
*** No rings associated ***                                              
                                                                         
Knowing nothing about certificates and key rings, I have several questions.  

Why would a certificate IBM needs to use be untrusted?
Can I just use a RACDCERT ALTER to make it TRUSTED?
Would it be safe to just TRUST the certificate?
It says "no rings associated".   Do I need to attach the cert to a keyring?  If 
so, what one(s)?  
From the looks of it, the download job "found" the certificate and was going to 
use it, but since it says untrusted, the job rejected it.  Is this correct?

Since this problem is somewhere between SMP/E and RACF, it's cross-post to 
IBM-Main and the RACF list.  

TIA,

Rex

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to