Hello,
I noticed that mpartner-default-abis was not present in the key_alias table. I therefore tried to upload the certificate provided in the documentation, but it was already expired
After uploading a new certificate that I generated, I started encountering an issue during the decryption step in mock-abis. This suggests that there is a key generation process that should have been performed beforehand, which I might have missed.
Could you please guide me on the correct procedure to generate the required keys? I also attempted to use the Key Manager UI in admin portal, but I could not proceed because the PARTNER application ID was not available as an input option.
I attempted to generate a CSR in KeyManager using the following parameters:
applicationId: PARTNER
referenceId: mpartner-default-abis
However, the API returned the following error:
KER-KMS-002 - ApplicationId not found in Key Policy. Key/CSR generation not allowed.
At the same time, the KeyManager logs indicate that during the ABIS flow the certificate lookup is performed with the same values:
applicationId: PARTNER
referenceId: mpartner-default-abis
Could you please provide guidance on how we should proceed so that we can successfully validate ABIS as a partner and complete the UIN generation process?