Why am I seeing a error in tenant storage configuration - "not found/unreachable" when I try to create an external queue?

Question

 I am trying to add an external queue,  but I'm getting this error:

ErrorValidation of the tenant storage configuration failed. 
See found errors in the section below An error was found in
 tenant storage configuration: 
Failed to connect to the messaging provider of 'from-reltio-temp' destination

"severity": "Error",
"errorMessage": "An error was found in tenant storage configuration: 
Message provider defined into the messaging section is unreachable",
"errorCode": 149,
"errorDetailMessage": "Validation of tenant storage configuration failed. 
Details: Message provider specified in the messaging section of the 
destination 'from_reltio_temp' was not found/unreachable.",
"innerErrorData": {
"exception": "com.reltio.metadata.errors.CommonException:Code: 
TENANT_CONFIGURATION_VALIDATION_ERROR; Message parameters: [Message provider 
defined into the messaging section is unreachable]. An error was found in 
tenant storage configuration: Message provider defined into the messaging section 
is unreachable. Validation of tenant storage configuration failed. Details: 
Message provider specified in the messaging section of the destination '<queuename>'
was not found/unreachable.",

Answer

• Verify the policy is correct.
• Make sure that the key is defined at the namespace level.
• Check the secret key's encoding. Please use a simple tool such as https://www.urlencoder.io/ to remove special characters such as + and /.

Encoding a key when it contains special characters is necessary to ensure it can be safely used in different contexts, such as URLs, JSON data, or database queries. Special characters can have specific meanings or functions in these contexts, which might lead to errors or security vulnerabilities if they are not correctly encoded.
Here are a few common scenarios where encoding is essential:
 

1. URL Encoding: URLs have a specific format and certain characters (like ?, &, =, #, etc.) have special meanings. If a key contains any of these characters, it needs to be URL-encoded to ensure it is interpreted correctly by web servers and browsers.
2. JSON Encoding: JSON is a text-based data format used to transmit data. Special characters in keys or values (like quotes, backslashes, etc.) must be escaped to ensure the JSON is correctly parsed.
3. Database Queries: In SQL queries, special characters in keys or values can lead to SQL injection attacks if not properly sanitized. Encoding helps to prevent these kinds of vulnerabilities.
4. HTML Encoding: When displaying keys in HTML, special characters like <, >, and & need to be encoded to prevent HTML injection attacks.

Encoding transforms special characters into a safe format that can be correctly interpreted in the intended context. For example, in URL encoding, a space character is converted to %20.