10:50 a.m.
Hi,
I just downloaded the 1.9.0 final release, started the standalone server, created the
initial admin user account and then tried to log in the admin console. I got the following
error at that point:
Failed client authentication: org.keycloak.authentication.AuthenticationFlowException:
Client was not identified by any client authenticator
The web page kept loading and the server had a lot of instance of the error above. I
couldn’t go any further. What did I miss?
Thanks,
Rong
12:26 a.m.
Were there any other exceptions in server.log at startup? Did you
migrate from previous version or started from clean DB? If migrated from
previous version, could you try with clean DB?
Thanks,
Marek
On 25/02/16 16:50, Rong Sang (CL-ATL) wrote:
Hi,
I just downloaded the 1.9.0 final release, started the standalone
server, created the initial admin user account and then tried to log
in the admin console. I got the following error at that point:
Failed client authentication:
org.keycloak.authentication.AuthenticationFlowException: Client was
not identified by any client authenticator
The web page kept loading and the server had a lot of instance of the
error above. I couldn’t go any further. What did I miss?
Thanks,
Rong
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
9:42 a.m.
Hi Marek,
That’s the first error I found in the server.log. There were many instances of the same
error. I didn’t find any other error.
I was testing the product on a mac. It was a clean install, no migration. I didn’t
configure SSL. According to 1.9.0 documents, it should work with localhost. The only
configuration I did was creating the initial admin user.
Thanks,
Rong
From: Marek Posolda <mposolda@redhat.com<mailto:mposolda@redhat.com>>
Date: Friday, February 26, 2016 at 12:26 AM
To: rongsang <rsang@carelogistics.com<mailto:rsang@carelogistics.com>>,
"keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>"
<keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>>
Subject: Re: [keycloak-user] "Client was not identified by any client
authenticator"
Were there any other exceptions in server.log at startup? Did you migrate from previous
version or started from clean DB? If migrated from previous version, could you try with
clean DB?
Thanks,
Marek
On 25/02/16 16:50, Rong Sang (CL-ATL) wrote:
Hi,
I just downloaded the 1.9.0 final release, started the standalone server, created the
initial admin user account and then tried to log in the admin console. I got the following
error at that point:
Failed client authentication: org.keycloak.authentication.AuthenticationFlowException:
Client was not identified by any client authenticator
The web page kept loading and the server had a lot of instance of the error above. I
couldn’t go any further. What did I miss?
Thanks,
Rong
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>https://lists.jboss.org/mailman/listinfo/keycloak-user<http://cp.mcafee.com/d/avndxMwcy1J5xZNxNxAsqejtPqdPhO-OOZtAsrhhhjpKUyYOrhKqenSmnHIL6QkkkSkknDSjsqr0y2Hr7PWApkDaRendSSfDR8OFelGsKr8eE-XpN_HYevKehu7tuVteVEVuV5xZAQsCzBdXG8FHnjlKUzOEuvkzaT0QSyrhdTV5xdVYsyMCqejtPpesRG9pxYGjFMygHiD00s4RtxxYGjB1SK5vbmfHFkKTjUCRlGQGuxEazW1fpYKrod7bXxI5-Aq83iSlYJo-KBiXtfyqnjh0q8x8-nMCq836Qd44aPd44AfxejILgd410Iq8dwmd45zVv2pEwRKpfUjBrpRyq8zoVYTOmewtduNP0J>
3:10 p.m.
Hmm.... So you just unpacked the ZIP, start the server, set the admin
password and then saw that error?
I didn't see it before tbh. Any chance to share whole stacktrace? And
what's your java version?
Marek
On 26/02/16 15:42, Rong Sang (CL-ATL) wrote:
Hi Marek,
That’s the first error I found in the server.log. There were many
instances of the same error. I didn’t find any other error.
I was testing the product on a mac. It was a clean install, no
migration. I didn’t configure SSL. According to 1.9.0 documents, it
should work with localhost. The only configuration I did was creating
the initial admin user.
Thanks,
Rong
From: Marek Posolda <mposolda(a)redhat.com <mailto:mposolda@redhat.com>>
Date: Friday, February 26, 2016 at 12:26 AM
To: rongsang <rsang(a)carelogistics.com
<mailto:rsang@carelogistics.com>>, "keycloak-user(a)lists.jboss.org
<mailto:keycloak-user@lists.jboss.org>" <keycloak-user(a)lists.jboss.org
<mailto:keycloak-user@lists.jboss.org>>
Subject: Re: [keycloak-user] "Client was not identified by any client
authenticator"
Were there any other exceptions in server.log at startup? Did you
migrate from previous version or started from clean DB? If migrated
from previous version, could you try with clean DB?
Thanks,
Marek
On 25/02/16 16:50, Rong Sang (CL-ATL) wrote:
> Hi,
>
> I just downloaded the 1.9.0 final release, started the standalone
> server, created the initial admin user account and then tried to log
> in the admin console. I got the following error at that point:
>
> Failed client authentication:
> org.keycloak.authentication.AuthenticationFlowException: Client was
> not identified by any client authenticator
>
> The web page kept loading and the server had a lot of instance of the
> error above. I couldn’t go any further. What did I miss?
>
> Thanks,
>
> Rong
>
>
>
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-user
5:04 p.m.
I’m using Java 8.
Here is the stacktrace of the error. Thanks!
2016-02-25 10:15:00,909 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025:
Keycloak 1.9.0.Final (WildFly Core 2.0.10.Final) started in 13660ms - Started 416 of 782
services (526 services are lazy, passive or on-demand)
2016-02-25 10:15:31,939 INFO [org.keycloak.services] (default task-2) KC-SERVICES0077:
Created initial admin user with username admin
2016-02-25 10:15:43,537 ERROR [org.keycloak.services] (default task-10) KC-SERVICES0014:
Failed client authentication: org.keycloak.authentication.AuthenticationFlowException:
Client was not identified by any client authenticator
at
org.keycloak.authentication.ClientAuthenticationFlow.processFlow(ClientAuthenticationFlow.java:101)
at
org.keycloak.authentication.AuthenticationProcessor.authenticateClient(AuthenticationProcessor.java:673)
at
org.keycloak.protocol.oidc.utils.AuthorizeClientUtil.authorizeClient(AuthorizeClientUtil.java:42)
at
org.keycloak.protocol.oidc.endpoints.TokenEndpoint.checkClient(TokenEndpoint.java:163)
at org.keycloak.protocol.oidc.endpoints.TokenEndpoint.build(TokenEndpoint.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
at
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:138)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:107)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:133)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:101)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
at
org.keycloak.services.filters.KeycloakSessionServletFilter.doFilter(KeycloakSessionServletFilter.java:78)
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
at
io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
at
io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
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)
2016-02-25 10:15:43,539 WARN [org.keycloak.events] (default task-10)
type=CODE_TO_TOKEN_ERROR, realmId=master, clientId=admin, userId=null,
ipAddress=127.0.0.1, error=invalid_client_credentials, grant_type=authorization_code
2016-02-25 10:15:44,344 ERROR [org.keycloak.services] (default task-42) KC-SERVICES0014:
Failed client authentication: org.keycloak.authentication.AuthenticationFlowException:
Client was not identified by any client authenticator
at
org.keycloak.authentication.ClientAuthenticationFlow.processFlow(ClientAuthenticationFlow.java:101)
at
org.keycloak.authentication.AuthenticationProcessor.authenticateClient(AuthenticationProcessor.java:673)
at
org.keycloak.protocol.oidc.utils.AuthorizeClientUtil.authorizeClient(AuthorizeClientUtil.java:42)
at
org.keycloak.protocol.oidc.endpoints.TokenEndpoint.checkClient(TokenEndpoint.java:163)
at org.keycloak.protocol.oidc.endpoints.TokenEndpoint.build(TokenEndpoint.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
at
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:138)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:107)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:133)
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:101)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
at
org.keycloak.services.filters.KeycloakSessionServletFilter.doFilter(KeycloakSessionServletFilter.java:78)
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
at
io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
at
io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
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)
From: Marek Posolda <mposolda@redhat.com<mailto:mposolda@redhat.com>>
Date: Friday, February 26, 2016 at 3:10 PM
To: rongsang <rsang@carelogistics.com<mailto:rsang@carelogistics.com>>,
"keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>"
<keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>>
Subject: Re: [keycloak-user] "Client was not identified by any client
authenticator"
Hmm.... So you just unpacked the ZIP, start the server, set the admin password and then
saw that error?
I didn't see it before tbh. Any chance to share whole stacktrace? And what's your
java version?
Marek
On 26/02/16 15:42, Rong Sang (CL-ATL) wrote:
Hi Marek,
That’s the first error I found in the server.log. There were many instances of the same
error. I didn’t find any other error.
I was testing the product on a mac. It was a clean install, no migration. I didn’t
configure SSL. According to 1.9.0 documents, it should work with localhost. The only
configuration I did was creating the initial admin user.
Thanks,
Rong
From: Marek Posolda <mposolda@redhat.com<mailto:mposolda@redhat.com>>
Date: Friday, February 26, 2016 at 12:26 AM
To: rongsang
<<mailto:rsang@carelogistics.com>rsang@carelogistics.com<mailto:rsang@carelogistics.com>>,
"keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>"
<keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>>
Subject: Re: [keycloak-user] "Client was not identified by any client
authenticator"
Were there any other exceptions in server.log at startup? Did you migrate from previous
version or started from clean DB? If migrated from previous version, could you try with
clean DB?
Thanks,
Marek
On 25/02/16 16:50, Rong Sang (CL-ATL) wrote:
Hi,
I just downloaded the 1.9.0 final release, started the standalone server, created the
initial admin user account and then tried to log in the admin console. I got the following
error at that point:
Failed client authentication: org.keycloak.authentication.AuthenticationFlowException:
Client was not identified by any client authenticator
The web page kept loading and the server had a lot of instance of the error above. I
couldn’t go any further. What did I miss?
Thanks,
Rong
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>https://lists.jboss.org/mailman/listinfo/keycloak-user<http://cp.mcafee.com/d/1jWVIi6h0SyM-U-yeovd79KVJ6VEVvppuKOedEEEFITshupdETd7bXbbRSnzqaaaraabPX9Kddwh1lJzVZicGjBqDbCXr7PWApkDaRendILEAbEefZvD6jhOMyeoWZOWqrzD8FKnuvj7th5dqWqJQkul3PWApmU6CQjq9K_8I3DATbL3HCXCM0tBKlJHL_O-8pFC20udCb5Ag8v3M91wu30YgEbu8P2MIw5yoobxwc0jcgF4Cj9yaM51cI1MN4C1gJY1xm0n3gGU0VkGl62Fm0sc2d1qdOOonye2M2y2NkeQ5_10o67gU5L1wnYY9k0GbTzhs1Bwoaxs3-p0HOroWropDUp6wOS6nMY2h01W2gEcE0c4DxsbM4jMa2oE61FIOl5d1dM762Qiq093bUuw6gfgIdygJUzcbbvg5x8QsH1U72gybzpoy5V1RXQo1sMYf0Ui4hB4o0FYOglt2UKl0E4y8j4wmu4w72joudqa0ayWI1Mazl0sg0of3nOUwbfcO63Me15iU53cw6CWm5E29eUIY7L5U3oAbfcK0ewMNEmgoo47g_N4d2F51x6Uqbf865k67NgcCkRxEM2Mamt2oycNm1pomu5axA3wAca-oCwS30Js23qGRqlfgQ5hZ0DI-ndCzAttYS2_id41Fra-mIvniFtKDNdbFEwd4gAvbUjd41zq6y25pCy2i7MD9SnE6y0wmd46Mb6y2NYLxcQgqTcDY9OJIWNd4hIs-rO4O3>
3074
days inactive
3075
days old
4 comments
2 participants
participants (2)
-
Marek Posolda -
Rong Sang (CL-ATL)