Chart 5.3.0: Mimir push API doesn't allow X-Scope-OrgID with special characters about mimir HOT 4 CLOSED

[..] clearly document what the new restrictions are and why

It seems that the issue is an degradation effect of #7700.

Note there is a document, that lists the requirements for tenant ID. It has the subset of special characters, that are supported. @bobbeeke, which of those listed aren't working for your setup?

from mimir.

Question marks in tenant IDs have never been allowed per the docs but this wasn't enforced when tenant federation was disabled until Mimir 2.12. Version 2.12 fixed this oversight.

PR: #6959
Changelog:

[CHANGE] Validate tenant IDs according to [documented behavior](https://grafana.com/docs/mimir/latest/configure/about-tenant-ids/) even when tenant federation is not enabled. Note that this will cause some previously accepted tenant IDs to be rejected such as those longer than 150 bytes or containing | characters. #6959

from mimir.

Clear, thanks for pointing out @narqo
I will change my X-Scope-OrgIDs.
It is however strange that until now I had no problem. I used random strings with all kind of characters and it did never complain.

Feel free to close this one if no further action is required.

from mimir.

Thank you, for having a look. If you further bump into an unexpected behaviour in the validation of the tenant's header, please re-open this one.

from mimir.