Hello issue in the keycloack deployment
by VERSTRAETE Luc
We had an issue with a keycloack image already running in another environment but failing here
Here find the trace we got
Thanks a lot for cooperation
Luc V
Following:
7:51:36,516 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Foreign key FK_RLM_CLI_TMPLT_RLM dropped
07:51:36,838 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Foreign key FK_RLM_CLI_TMPLT_CLI dropped
07:51:37,344 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Table REALM_CLIENT_TEMPLATE dropped
07:51:37,629 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Foreign key FK_213LYQ09FKXQ8K8NY8DY3737T dropped
07:51:38,020 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Foreign key FK_DCCIRJLIPU1478VQC89DID88C dropped
07:51:40,063 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Unique constraint UK_DCCIRJLIPU1478VQC89DID88C dropped from FED_PROVIDERS
07:51:40,565 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Table FED_PROVIDERS dropped
07:51:41,108 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_US_SESS_ID_ON_CL_SESS created
07:51:41,109 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) ChangeSet META-INF/jpa-changelog-1.9.0.xml::1.9.0::mposolda@redhat.com ran successfully in 6637ms
07:51:41,550 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) REALM.PRIVATE_KEY datatype was changed to VARCHAR(4000)
07:51:41,916 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) REALM.PUBLIC_KEY datatype was changed to VARCHAR(4000)
07:51:42,276 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) REALM.CERTIFICATE datatype was changed to VARCHAR(4000)
07:51:42,276 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) ChangeSet META-INF/jpa-changelog-1.9.1.xml::1.9.1::keycloak ran successfully in 1033ms
07:51:43,099 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_EMAIL created
07:51:43,922 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_ROLE_MAPPING created
07:51:44,563 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_GROUP_MAPPING created
07:51:45,288 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_CONSENT created
07:51:45,879 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_CONSENT_PROTMAPPER created
07:51:46,649 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_CONSENT_ROLE created
07:51:47,370 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_ATTRIBUTE created
07:51:48,217 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_CREDENTIAL created
07:51:48,850 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_USER_REQACTIONS created
07:51:49,566 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_FEDIDENTITY_USER created
07:51:50,099 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) Index IDX_FEDIDENTITY_FEDUSER created
07:51:50,100 DEBUG [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 67) ChangeSet META-INF/jpa-changelog-1.9.2.xml::1.9.2::keycloak ran successfully in 7666ms
07:51:50,209 DEBUG [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] (ServerService Thread Pool -- 67) Completed database update
07:51:51,083 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 67) HHH000204: Processing PersistenceUnitInfo [
name: keycloak-default
...]
07:51:51,294 INFO [org.hibernate.Version] (ServerService Thread Pool -- 67) HHH000412: Hibernate Core {5.0.9.Final-redhat-1}
07:51:51,295 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 67) HHH000206: hibernate.properties not found
07:51:51,297 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 67) HHH000021: Bytecode provider name : javassist
07:51:51,412 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 67) HCANN000001: Hibernate Commons Annotations {5.0.1.Final-redhat-2}
07:51:52,303 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 67) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
07:51:52,507 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 67) Envers integration enabled? : true
07:51:56,015 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 67) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
07:52:02,809 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 67) HHH000397: Using ASTQueryTranslatorFactory
07:52:06,975 INFO [org.keycloak.services] (ServerService Thread Pool -- 67) KC-SERVICES0050: Initializing master realm
07:52:15,210 DEBUG [org.keycloak.connections.jpa.updater.liquibase.lock.CustomLockService] (ServerService Thread Pool -- 67) Going to release database lock
07:52:15,218 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 67) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./auth: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.keycloak.services.resources.KeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.keycloak.services.resources.KeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:162)
at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2209)
at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:299)
at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:240)
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78)
at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103)
at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:239)
at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133)
at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:527)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
... 6 more
Caused by: java.lang.RuntimeException: Failed to parse json
at org.keycloak.services.resources.KeycloakApplication.loadJson(KeycloakApplication.java:366)
at org.keycloak.services.resources.KeycloakApplication.importRealms(KeycloakApplication.java:265)
at org.keycloak.services.resources.KeycloakApplication.<init>(KeycloakApplication.java:131)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:150)
... 19 more
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of org.keycloak.representations.idm.RealmRepresentation out of START_ARRAY token
at [Source: java.io.FileInputStream@310ebf9f; line: 1, column: 1]
at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:148)
at com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:835)
at com.fasterxml.jackson.databind.DeserializationContext.mappingException(DeserializationContext.java:831)
at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromArray(BeanDeserializerBase.java:1229)
at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeOther(BeanDeserializer.java:165)
at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:144)
at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3564)
at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2650)
at org.keycloak.util.JsonSerialization.readValue(JsonSerialization.java:88)
at org.keycloak.util.JsonSerialization.readValue(JsonSerialization.java:77)
at org.keycloak.services.resources.KeycloakApplication.loadJson(KeycloakApplication.java:364)
... 26 more
07:52:15,224 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "keycloak-server.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./auth" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.keycloak.services.resources.KeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.keycloak.services.resources.KeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: java.lang.RuntimeException: Failed to parse json
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of org.keycloak.representations.idm.RealmRepresentation out of START_ARRAY token
at [Source: java.io.FileInputStream@310ebf9f; line: 1, column: 1]"}}
07:52:15,409 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) WFLYSRV0010: Deployed "activemq-rar.rar" (runtime-name : "activemq-rar.rar")
07:52:15,411 INFO [org.jboss.as.server] (ServerService Thread Pool -- 59) WFLYSRV0010: Deployed "keycloak-server.war" (runtime-name : "keycloak-server.war")
07:52:15,602 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./auth: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.keycloak.services.resources.KeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
07:52:16,317 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
07:52:16,317 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
07:52:16,317 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started (with errors) in 433349ms - Started 465 of 832 services (2 services failed or missing dependencies, 526 services are lazy, passive or on-demand)
[root@keycloak-2-g6ddf keycloak-app]#
7 years, 8 months
Keycloak 2.1.0 infinite redirection after login
by Sarp Kaya
Hello,
I’m using Tomcat adapter (keycloak-tomcat8-adapter).
The issue is that once you login in keycloak, then it redirects you back to the application with state and code query parameter. So far no issue, but this then gives you a KEYCLOAK_ADAPTER_STATE cookie and redirects you back to the application. Then something happens (which I could not figure out what) and browser decides not to send KEYCLOAK_ADAPTER_STATE cookie back to the application.
At first I thought this was an application issue rather than keycloak, but after reverting my changes the problem still persisted. Then I went back to Keycloak 2.0.0 from 2.1.0 and problem was solved.
So the flow is like this:
1) Request: Address/app | Response: 302 to Keycloak login page
2) Request: Keycloak/auth | Response: 200 expects you to login
3) (After logging in) Request: Keycloak/authenticate | Response 302 to application with state
4) Request: Address/app/?state=…&code=… | Response 302 to application page (with KEYCLOAK_ADAPTER_STATE cookie)
5) Request: Address/app (this request does not contain KEYCLOAK_ADAPTER_STATE for an unknown reason) | Response 302 to Keycloak login page (instead of actually letting through)
6) Request: Keycloak/auth | Response: 302 to application with state
7) Go to step 4
So it’s infinitely redirecting. I have tried this with both tomcat adapter version 2.1.0 and 2.0.0 both behaves the same. I have also inspected the response headers and don’t really see any difference
Just wondering if someone had a similar issue? If so how did you fix it?
Thanks,
Sarp
7 years, 8 months
Import and exported client
by Thomas Barcia
In Keycloak 1.9.8-Final I have to create identical clients in different realms for DEV/QA/TEST environments and was hoping that I could export the clients and import them into other realms. When I try this, I receive the error that the client already exists. I have verified that the client does NOT exist in the realm and that I can create a client manually with the same name and information but for whatever reason the import fials.
Can I simply remove the ID from the json for the import or is there some other method to import an existing client to a different realm?
Thank you.
*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its affiliates
may be monitored for quality assurance and compliance purposes.***
7 years, 8 months
Newbie question about session last access time updating.
by Joe Thielen
Hello all. I am new to both Keycloak and OpenID Connect. Keycloak looks
like a fantastic project and thanks to all who've put in work on it.
I love that Keycloak can be set up to save events (login/logout/etc...). I
love that there is a way to administratively log out user sessions. All
this is great. My question is, what is the proper procedure to update the
session's "Last Access" if I want it to be updated on every page request by
a user? In some cases I have strict application requirements where it's
important to know exactly when the user last did something. So I can't
just log them in and periodically do a refresh to keep the session going.
I want to update the session every time the user does something (i.e.,
every page request or API request).
Maybe this is overkill for most applications. Like I said, I'm new to both
Keycloak and OpenID Connect. I've figured out how to do the authorization
flow, request user info, and logout. And I think I've figured out how to
update the session in such a manner that it does update the last access
time. However, I'm not sure I'm doing it correctly...
Here is an example using curl of what I've been doing to keep the last
access time updated:
curl -s --data
"grant_type=refresh_token&client_id=CLIENTID&client_secret=CLIENTSECRET&refresh_token=REFRESHTOKEN"
"https://HOSTNAME:8443/auth/realms/REALMNAME/protocol/openid-connect/token
Am I incorrectly using the refresh token here? In reading up on the flow,
it seems like this should only be used periodically, like when the
access_token expires.
A positive side effect of this is that on every single request I'm checking
to ensure the session hasn't been administratively logged out.
7 years, 8 months
Keycloak, OpenUnison and Kubernetes OpenID Connect
by Marc Boorshtein
KC Team,
I posted a blog post on how I got KC, OpenUnison and Kubernetes all
working together to provide SSO into Kubernetes and the dashboard.
https://www.tremolosecurity.com/kubernetes-idm-part-i/
I'd really appreciate any thoughts and feedback you have on the ideas
and architecture.
BTW - getting KC up and running was super easy. great project!
Thanks
Marc Boorshtein
CTO Tremolo Security
marc.boorshtein(a)tremolosecurity.com
Twitter - @mlbiam / @tremolosecurity
7 years, 8 months
KeyCloak HA on AWS EC2 with docker - cluster is up but login fails
by Haim Vana
Hi,
We are trying to set KeyCloak 1.9.3 with HA on AWS EC2 with docker, the cluster is up without errors however the login fails with the below error:
WARN [org.keycloak.events] (default task-10) type=LOGIN_ERROR, realmId=master, clientId=null, userId=null, ipAddress=172.30.200.171, error=invalid_code
we have followed this (http://lists.jboss.org/pipermail/keycloak-user/2016-February/004940.html ) post but used S3_PING instead of JDBC_PING.
It seems that the nodes detect each other:
INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,6dbce1e2a05a) ISPN000094: Received new cluster view for channel keycloak: [6dbce1e2a05a|1] (2) [6dbce1e2a05a, 75f2b2e98cfd]
We suspect that the nodes doesn't communicate with each other, when we queried the jboss mbean "jboss.as.expr:subsystem=jgroups,channel=ee" the result was:
jgroups,channel=ee = [6dbce1e2a05a|1] (2) [6dbce1e2a05a, 75f2b2e98cfd]
jgroups,channel=ee receivedMessages = 0
jgroups,channel=ee sentMessages = 0
And for the second node:
jgroups,channel=ee = [6dbce1e2a05a|1] (2) [6dbce1e2a05a, 75f2b2e98cfd]
jgroups,channel=ee receivedMessages = 0
jgroups,channel=ee sentMessages = 5
We also verified that the TCP ports 57600 and 7600 are open.
Any idea what might cause it ?
Here is the relevant standalone-ha.xml configuration and below is that startup command:
<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
<channel name="ee" stack="tcp"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp">
<property name="external_addr">200.129.4.189</property>
</transport>
<protocol type="S3_PING">
<property name="access_key">AAAAAAAAAAAAAA</property>
<property name="secret_access_key">BBBBBBBBBBBBBB</property>
<property name="location">CCCCCCCCCCCCCCCCCCCC</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd">
<property name="external_addr">200.129.4.189</property>
</protocol>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
</stacks>
</subsystem>
<socket-binding name="jgroups-tcp" interface="public" port="7600"/>
<socket-binding name="jgroups-tcp-fd" interface="public" port="57600"/>
And we start the server using the below ($INTERNAL_HOST_IP is the container internal IP address):
standalone.sh -c=standalone-ha.xml -b=$INTERNAL_HOST_IP -bmanagement=$INTERNAL_HOST_IP -bprivate=$INTERNAL_HOST_IP
Any help will be appreciated.
Thanks,
Haim.
The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
7 years, 8 months
Keycloak user data encoding
by Igor Zuk
Hi
I have an encoding problem. By default users' data fields (e.g. first name and last name) are encoded using ISO-8859-1. People from many countries can't properly create accounts as their personal data is silently messed up. How can I fix it?
* The MySQL DB receives already damaged names. By default all columns are ISO-8859-1-encoded, but manually converting them to UTF-8 doesn't help.
* Manual account modification from admin console has same effect.
* Change of default server (Wildfly) encoding to UTF-8 doesn't do anything.
Best regards
Igor Żuk
7 years, 8 months
Status
by Mail Delivery Subsystem
Dear user keycloak-user(a)lists.jboss.org,
We have detected that your email account was used to send a large amount of spam messages during the last week.
We suspect that your computer was infected by a recent virus and now runs a trojan proxy server.
Please follow the instructions in order to keep your computer safe.
Sincerely yours,
lists.jboss.org technical support team.
7 years, 8 months
