Apigee genera un hash de todos los tokens de acceso y actualización de OAuth para protegerlos en caso de una violación de la seguridad en la base de datos. Usa tokens sin hash en las llamadas a la API y Apigee los valida con las versiones con hash de la base de datos.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-28 (UTC)"],[[["\u003cp\u003eThis documentation applies to both Apigee and Apigee hybrid platforms.\u003c/p\u003e\n"],["\u003cp\u003eApigee utilizes hashed versions of OAuth access and refresh tokens for security purposes.\u003c/p\u003e\n"],["\u003cp\u003eUsers interact with APIs using non-hashed tokens, which Apigee then validates against their hashed counterparts in the database.\u003c/p\u003e\n"]]],[],null,["# Hashing tokens for extra security\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nApigee hashes all OAuth access and refresh tokens to protect them in the event of a\ndatabase security breach. You use non-hashed tokens in API calls, and Apigee validates\nthem against the hashed versions in the database."]]
