A cormorant-roost daemon still ships a client secret in source control to authenticate to Microsoft Entra ID. What credential approach should the developer prefer?
Select an answer to reveal the explanation.
Short Explanation
Secrets in the repo are a spill waiting to happen. Prefer a certificate on the app registration—or a managed identity when Azure is already hosting the daemon.
Full Explanation
Confidential clients authenticate to Entra with a client secret or a certificate credential; certificates avoid long-lived secrets in configuration and source control. When the workload runs on Azure, managed identity removes the need to provision app secrets for many resource-to-resource scenarios. Storing secrets in repositories remains a common anti-pattern.