# 307 Temporary redirect during /login/callback call in SSO (prodigy\[company\])

**URL:** <https://support.prodi.gy/t/307-temporary-redirect-during-login-callback-call-in-sso-prodigy-company/7149>\
**Category:** Uncategorized\
**Tags:** usage\
**Created:** [March 12, 2024, 9:30am UTC](https://support.prodi.gy/t/307-temporary-redirect-during-login-callback-call-in-sso-prodigy-company/7149 "2024-03-12T09:30:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![marcoB](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@marcoB](https://support.prodi.gy/u/marcoB)\
**Post date:** [March 14, 2024, 1:06pm UTC](https://support.prodi.gy/t/307-temporary-redirect-during-login-callback-call-in-sso-prodigy-company/7149/5 "2024-03-14T13:06:43Z")

</div>

Thank you @magdaaniol

Following up with the IT team, it seems that (if I understand correctly) before authentication, prodigy sends a request with the following: ` __prodigy_cauth_id_token__ ` and ` __prodigy_cauth_access_token__ ` . This results in big headers (over 4k) which are blocked by the gateway.

Could you suggest any workaround from prodigy side?

---

_[View the full topic](https://support.prodi.gy/t/307-temporary-redirect-during-login-callback-call-in-sso-prodigy-company/7149)._