Config-Hub Deployment Error

Hello Experts ,

I am trying to import a Source using Config-Hub , from one tenant to another .
I resolved the reference issues , But while deploying I am encountering the following error:
Sensitive data found but encryption key was unavailable: password

The config file contains password key , and is under encrypted attributes as well (this is a web service connector)

What I have tried :

  • Removing all the encrypted password values and placing with “”
  • Removed all values in encrypted attribute of source config

But no luck . Is anyone aware of this error ?

Thank You ,
Sid

Hi @sidharth_tarlapally ,

Have you tried deploying by removing the password attribute or the by removing all the encrypted attributes totally?

@GOKUL_ANANTH_M

I tried both ways

@sidharth_tarlapally -
I want to be transparent with you. based on debugging this issue i got this information. see this information might be useful to you.
In the source tenant, locate the encryption key file used for encrypting sensitive data.
Copy this encryption key file to the destination tenant.
In the destination tenant, configure the Connector Gateway to use this encryption key file. 4. Edit the init.xml file in the Connector Gateway of the destination tenant.
Add the following line to the init.xml file, specifying the path to the copied encryption key file:
path/to/your/encryption/key/file
For example: C:\FileName
Ensure that the key length in the encryption file is 16, 24, or 32 bytes.
Save the init.xml file and restart the Connector Gateway service.
By following these steps, you should be able to import the Source using Config-Hub from one tenant to another without encountering the encryption key error. The destination tenant will now have access to the necessary encryption key to decrypt the sensitive data during the import process.

Bro, anything that PII consider sensitive is redacted .

So you need to check if there is any other PII information in your connector.
SImple as that.

Hi @ipobeidi

I tried to import by removing all this PII data . But still the same .