New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting TYK_GW_HASHKEYFUNCTION changes key format #5558
Labels
Comments
Was able to find the description here #1753 |
This also makes the loggin statement useless as the key suffix is always one of the three e.g.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Branch/Environment/Version
Describe the bug
This is an unexpected and undocumented behaviour
If I only set
TYK_GW_HASHKEYS=true
the keys generated by tyk are of the form:[email protected]
If I set TYK_GW_HASHKEYFUNCTION to any value (murmur64, murmur128, sha256) the returned key is now a base64 encoded json, e.g.
eyJvcmciOiIxMjNAZXhhbXBsZS5jb20iLCJpZCI6Ijk5NzhkZDk0MGNkMzQ5YmNhZWY3YmQyMDQxNGY3YmMyIiwiaCI6InNoYTI1NiJ9
Which when decoded is
Reproduction steps
Set
TYK_GW_HASHKEYFUNCTION
to any valueActual behavior
Key format changes
Expected behavior
Key format doesn't change
Additional context
This significantly increases the key size, which is a concern given that each API request includes in in the header.
The text was updated successfully, but these errors were encountered: