+1

Hi Braden, there is currently no declarative way to work around this, but a feature enhancement to allow tokens/headers larger than 256 characters is being tracked by our product team. We do not have an ETA for this improvement, but will update this post once we do.

Is there any update on this?  I’m having the same issue where an authentication token for a REST endpoint has a token with a length > 256.  Is there a workaround or timeline?

Thanks!