{"section":"known-issues","requestedLocale":"en","requestedSlug":"impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls","locale":"en","slug":"impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls","path":"docs/en/known-issues/Store Framework/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md","branch":"main","content":"## Summary\n\n\nWhen you are in telemarketing access and try to impersonate access of a user that has an access to a trade policy with restrictions, some graphql layers are not sending the impersonated user cookie, causing a forbidden access response from APIs\n\n\n##\n\n## Simulation\n\n\n\n1. Create an admin user with call center access\n2. Create a TP with a restriction\n3. Create a user into the account and grant access to the closed TP condition through the master data\n4. Log into the account with the call center user-created at step 1\n5. Impersonate the user created at step 3\n6. Check any PDP\n\nThe expected behavior is not found on page, due to the authentication used is not allowed to access impersonated's user TP and we are not sending the impersonated session for some Graphql calls\n\n\n##\n\n## Workaround\n\n\n\n\n1. Create a user in the store with the same email from the admin's access\n2. Grant access to the tp condition for the admin's email\n\nWith that, you will be able to access impersonated's user conditions"}