Before reporting an issue

• I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

organizations

Describe the bug

Different MySQL/MariaDB versions could have different settings character sets and collations. There was reported issue #45239 which was caused by mismatch of charset.

It was fixed by setting specific charset for some columns to utf8mb3 with collation utf8mb3_unicode_ci.

This decision cased an issue with other deployments where could have been used the same charset, but different collation: #45526

Therefore we revisited the approach to rely on database defaults when creating new tables and columns etc. This issue will "revert" the change to updated columns back to database defaults and documents the expectation that before migrating keycloak, the database is in consistent state and default charset and collation matches.

Version

26.5.1

Regression

• The issue is a regression

Expected behavior

see description

Actual behavior

see description

How to Reproduce?

see description

Anything else?

No response