safe-dto

To prevent sensitive data from leaking in API responses, you map entities containing passwords, keys, or tokens to Safe DTOs before sending data to the client. This approach omits confidential fields from the response payload.

A Safe DTO is a type-safe response schema, identified by a Safe prefix like SafeMediaSource, that excludes confidential fields. It secures backend responses by mapping sensitive entities to these restricted schemas before client delivery.

You map sensitive user profile entities to safe response objects by implementing mapping functions that transform full entities into Safe-prefixed DTOs. These functions explicitly omit confidential fields like passwords and tokens from the output.

You need Safe DTO mappings when backend services return data containing passwords, keys, or tokens. Use cases include securing user account data, session information, and configuration data in API responses to prevent information leakage.

Yes, the Safe DTO pattern works for securing configuration data with API keys. It provides mapping functions that omit confidential fields from configuration entities, ensuring sensitive keys are excluded before the response is sent.

A limitation of using Safe-prefix schemas is that developers must manually implement and maintain the mapping functions for each entity type. If a new sensitive field is added to the source entity, the Safe DTO mapping must be updated to prevent leakage.