{"version":"2.1.233","anchor":"gateway-requests-carry-the-signed-in-user-s-identity","canonical_anchor":"gateway-requests-carry-the-signed-in-user-s-identity","heading":"Gateway requests carry the signed-in user's identity","tier":"internal","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/gateway-requests-carry-the-signed-in-user-s-identity","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Gateway requests carry the signed-in user's identity\n\nProxy requests now attach your signed-in subject and email unless a managed principal is used.\n\n**What**\n\nRequests through the proxy path that are not made under a managed service principal now attach the user's subject and email, and pass the same pair to the model-list callback. Previously only the principal marker was attached.\n\n**Evidence**\n\n`criPrincipal`\n\n- Area: Gateway\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}