Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-3873

Failure to initialize database with MySQL using UTF8

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • 2.3.0.Final
    • None
    • Storage
    • None
    • Hide

      Use this docker-compose setup:

      version: '2'
services:
  mysql:
    image: mariadb:10.1
    expose:
      - "3306"
    environment:
      MYSQL_ROOT_PASSWORD: openidctest
      MYSQL_DATABASE: keycloak
      MYSQL_USER: keycloak
      MYSQL_PASSWORD: keycloak
    command:
      - --character-set-server=utf8mb4
      - --collation-server=utf8mb4_unicode_ci
  keycloak:
    image: jboss/keycloak-mysql:2.3.0.Final
    links:
      - mysql
    environment:
      KEYCLOAK_USER: admin
      KEYCLOAK_PASSWORD: openidctest
      MYSQL_DATABASE: keycloak
      MYSQL_USER: keycloak
      MYSQL_PASSWORD: keycloak
      # Workaround for container using legacy Docker links, resulting in
      # "WFLYCTL0211: Cannot resolve expression 'jdbc:mysql://${env.MYSQL_PORT_3306_TCP_ADDR}:${env.MYSQL_PORT_3306_TCP_PORT}
      MYSQL_PORT_3306_TCP_ADDR: mysql
      MYSQL_PORT_3306_TCP_PORT: "3306"
      Show
      Use this docker-compose setup: version: '2' services: mysql: image: mariadb:10.1 expose: - "3306" environment: MYSQL_ROOT_PASSWORD: openidctest MYSQL_DATABASE: keycloak MYSQL_USER: keycloak MYSQL_PASSWORD: keycloak command: - --character-set-server=utf8mb4 - --collation-server=utf8mb4_unicode_ci keycloak: image: jboss/keycloak-mysql:2.3.0.Final links: - mysql environment: KEYCLOAK_USER: admin KEYCLOAK_PASSWORD: openidctest MYSQL_DATABASE: keycloak MYSQL_USER: keycloak MYSQL_PASSWORD: keycloak # Workaround for container using legacy Docker links, resulting in # "WFLYCTL0211: Cannot resolve expression 'jdbc:mysql: //${env.MYSQL_PORT_3306_TCP_ADDR}:${env.MYSQL_PORT_3306_TCP_PORT} MYSQL_PORT_3306_TCP_ADDR: mysql MYSQL_PORT_3306_TCP_PORT: "3306"
    • -

    Description

      With a MySQL database using UTF8, Keycloak initialization will fail with error "Specified key was too long; max key length is 767 bytes" (see attached log for details).

      A workaround is to create the keycloak database with latin1 charset. If you do want UTF8 however, resources I found on this error in other applications recommend choosing a different key.

      I tried --innodb-large-prefix=1 but it didn't help.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. KEYCLOAK-3439 MySQL UTF-8 encoding

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Enhancement - An enhancement or refactoring of existing functionality KEYCLOAK-13305 Make Keycloak MySQL utf8mb4 ready

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Activity

            People

              hmlnarik@redhat.com Hynek Mlnařík
              solsson Staffan Olsson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: