Salesforce Certified MuleSoft Platform Architect free question 6 / 10 · Domain 5: Governing web APIs on Anypoint Platform
A security audit finds that, on a company's own server running Mule Gateway, client secrets sit in memory in their original form. Which response matches the documentation on credentials hashing?
- Start Mule with anypoint.platform.hash_clients enabled, so that only the client secret is stored hashed with SHA-256
- Do not change the configuration because hashing is on by default, and answer the audit by confirming in the logs that it is on
- Enable hash_clients and encryption together, so that the contract information in memory is hashed and then encrypted
- Start Mule with anypoint.platform.hash_clients enabled, so that the client ID and the client secret are stored hashed
Show the answer and explanation
Answer: A
Why this is correct
The page explains that enabling client hashing hides client secrets from the Mule server: Mule Gateway still stores the client credentials in memory, but only the client secret is hashed, using SHA-256. Client hashing is disabled by default. To enable it, start the Mule server with the anypoint.platform.hash_clients property enabled, either on the start command with -M-Danypoint.platform.hash_clients=true or in wrapper.conf. Changing the setting and restarting does not affect the processing of incoming requests.
Why the other options are wrong
"Start Mule with anypoint.platform.hash_clients enabled, so that the client ID and the client secret are stored hashed" … The page says Mule Gateway stores the client credentials in memory with only the client secret hashed, so the client ID is left as it is.
"Do not change the configuration because hashing is on by default, and answer the audit by confirming in the logs that it is on" … The page says client hashing is disabled by default, so the secret is stored in its original form until the property is enabled.
"Enable hash_clients and encryption together, so that the contract information in memory is hashed and then encrypted" … The page says that if both encryption and hashing are enabled, the contract information in memory is hashed but not encrypted.
The wrapper.conf entry
When adding a wrapper.java.additional.<n> line to wrapper.conf, number the entries consecutively so Java reads the property. You can confirm that hashing is on by turning on DEBUG for the Mule gateway deployment logger and looking for the line about the SHA-256 hashing algorithm.