ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SMP/E Receive Order: faultcode = Client.Authentication.NotRecognizedClient.Authentication.NotRecognized

book

Article ID: 238912

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS

Issue/Introduction

Existing SMPE Receive Order client certificate was about to expire, so a new client certificate was downloaded, installed, and connected it to the appropriate keyring.

Attempted to run RECEIVE ORDER job fails with an invalid client certificate error.

GIM69188S ** RECEIVE PROCESSING HAS FAILED. AN ERROR WAS FOUND IN THE RESPONSE RECEIVED FROM THE SERVER AT
             https://eapi.broadcom.com/receiveorder.
GIM69226I    faultcode = Client.Authentication.NotRecognizedClient.Authentication.NotRecognized.
GIM69226I    faultstring = Invalid client certificate..
GIM69226I    description = Invalid client certificate..
GIM20501I    RECEIVE PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12.

Cause

Unknown problem occurred during download, install, connect process.

Environment


SMP/E Internet Service Retrieval (aka.RECEIVE ORDER)

Resolution

Redo the process from the beginning...

The below examples are applicable to IBM RACF. For TSS or ACF2, please refer to Configure SMP/E Internet Service Retrieval for complete information.

1. Download the client (user) certificate.

2. Upload the certificates from your desktop to z/OS.
 
- Upload the certificates as text (ASCII) data to your z/OS system in RECFM=VB and LRECL>=84 format (Note: may use LRECL>=84)
 
- When uploading the certificate to z/OS, specify the WRAP parameter to ensure that the data is wrapped to the next record if no new line character is encountered before the logical record length of the receiving file is reached.
 
- If you use FTP, use the following FTP commands to avoid any truncation:
 
  ASCII QUOTE SITE WRAP LRECL=84 RECFM=VB
  PUT cert_file_name 'your.mvs.dataset.name' (REPLACE
  quit
 
- When done correctly, you should be able to browse the z/OS dataset and see that the file contains -----BEGIN CERTIFICATE-----. at the beginning and -----END CERTIFICATE-----. at the end.
 
3. Add the User certificate to your RACF database:
 
RACDCERT ID(certificate-owner) ADD('your.mvs.dataset.name') +
WITHLABEL('your User certificate label') TRUST
 
4. Connect the certificates to the keyring:
 
RACDCERT ID(ring-owner) CONNECT(LABEL('SMPE Client Certificate') +
RING(keyringname) USAGE(CERTAUTH) )