A software engineering team is developing a backend service that must automatedly transmit sensitive transaction audit logs to an external analytics vendor's endpoint. The security team specifies that the integration must eliminate static, long-lived API keys in application configuration files and support short-lived, cryptographically verifiable tokens for machine-to-machine authentication. Which of the following identity and access management architecture solutions should be implemented to satisfy these requirements?
- Implement OAuth 2.0 Client Credentials Grant to request short-lived JSON Web Tokens (JWTs) directly from the vendor's authorization server.Cevap
- BConfigure SAML 2.0 Web Browser Single Sign-On (SSO) using identity provider metadata and XML-based authentication assertions for the service account.
- CRestrict endpoint traffic using IP address whitelisting and HTTP Basic Authentication over an isolated network tunnel.
- DDeploy an inline Web Application Firewall (WAF) to inspect outgoing HTTP payloads for hardcoded API key patterns before transmission.
Cevap
Implementing OAuth 2.0 Client Credentials Grant with short-lived JSON Web Tokens (JWTs) issued by the vendor's authorization server provides secure, automated machine-to-machine authentication without static credentials.
The correct solution uses the OAuth 2.0 Client Credentials grant, which allows a client service to authenticate directly with an authorization server using its client credentials and obtain a short-lived JSON Web Token (JWT). This satisfies both the machine-to-machine automation requirement and the security policy prohibiting static long-lived keys.
Adım Adım Çözüm
Anahtar Kavram
Machine-to-Machine (M2M) Authentication and OAuth 2.0 Client Credentials Grant