Repository navigation
Replies: 1 comment 6 replies
Remove the respective environment variables.
This was discussed a little in #20460 and the associated issue. I don't believe that the warning is meaningful for the initial start while the database schema is being initialized. cc @ahus1
See https://www.keycloak.org/server/hostname#_exposing_the_administration_console_on_a_separate_hostname |
|
You are using hostname v2, those are hostname v1 properties and no longer used. |
|
Sorry i meant the admin console hostname, it says on that link to do start --hostname https://my.keycloak.org --hostname-admin https://admin.my.keycloak.org:8443 but can i do like KC_HOSTNAME_ADMIN? |
|
See https://www.keycloak.org/server/configuration and https://www.keycloak.org/server/all-config - yes every config option supports an env variable. |
|
Alright!, may i borrow this for another question that came up regarding setup environments? |
|
@SekSion you should start a new dicussion for additional topics. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
as the title says im setting up keycloak on AWS ECS + Fargate and using loadbalancers to use my SSL, i also have a subdomain with route53 pointing to auth.[domain], and these are my current env variables, Also using the command START not start-dev
Note: Empty values are just secrets :)
KC_BOOTSTRAP_ADMIN_PASSWORD =
KC_BOOTSTRAP_ADMIN_USERNAME =
KC_DB = mysql
KC_DB_PASSWORD =
KC_DB_URL = jdbc:mysql://
KC_DB_USERNAME =
KC_HEALTH_ENABLED = true
KC_HOSTNAME = auth.[domain].com
KC_HOSTNAME_STRICT = true
KC_HOSTNAME_STRICT_HTTPS = true
KC_HTTP_ENABLED = true
KC_LOG_LEVEL = INFO
KC_PROXY = edge
KC_PROXY_HEADERS = xforwarded
what people suggest to improve security with latest trends and also i have these errors / warning on console any suggestions on how tto fix them?
"(main) Hostname v1 options [proxy, hostname-strict-https] are still in use, please review your configuration"
"(main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use or to re-specify all configuration if this is the case"
And lastly what do i need so i can have the console on a different route to be more secure?
All reactions