Proxy configuration issue
by Adrian Matei
Hi everyone,
I am trying to make a simple test and configure a keycloak proxy to protect
an application running on http://localhost:8280/backend/
1.
My proxy.json configuration looks like the following:
{
"target-url": "http://localhost:8280/",
"send-access-token": false,
"bind-address": "localhost",
"http-port": "8080",
"applications": [
{
"base-path": "/backend",
"error-page": "/error.html",
"adapter-config": {
"realm": "demo",
"resource": "sandbox-backend",
"realm-public-key":
"MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrVrCuTtArbgaZzL1hvh0xtL5mc7o0NqPVnYXkLvgcwiC3BjLGw1tGEGoJaXDuSaRllobm53JBhjx33UNv+5z/UMG4kytBWxheNVKnL6GgqlNabMaFfPLPCF8kAgKnsi79NMo+n6KnSY8YeUmec/p2vjO2NjsSAVcWEQMVhJ31LwIDAQAB",
"auth-server-url": "http://localhost:8180/auth",
"ssl-required" : "external",
"credentials": {
"secret": "9323cdd6-7e0e-46ce-814f-b5ac79581395"
}
}
}
]
}
2.
I've started the proxy server as specified in the documentation "java -jar
bin/launcher.jar proxy.json"
I am getting an error "ERROR: UT005026: Jetty ALPN support not found on
boot class path, SPDY client will not be available.", but the server still
starts, I don't think there should be a problem with that...
3. In the admin console (keycloak running on port 8180) I've configured the
backend application like the following:
Could you tell me what I am doing wrong? When I put in the app's url in the
browser it goes directly to the application...
Thanks,
Adrian
8 years, 5 months
Defect in the OIDCAttributeMapperHelper class
by Jeff Macomber
HI,
I believe i have come across a defect in the OIDCAttributeMapperHelper
class. The issue occurs when you have a String Attribute which is set with
no value using a custom federation provider. The code blows up on the line:
return attributeValue.toString(); (Line 64)
in the section of code:
String type = mappingModel.getConfig().get(JSON_TYPE);
if (type == null) return attributeValue;
if (type.equals("boolean")) {
if (attributeValue instanceof Boolean) return attributeValue;
if (attributeValue instanceof String) return
Boolean.valueOf((String)attributeValue);
throw new RuntimeException("cannot map type for token claim");
} else if (type.equals("String")) {
if (attributeValue instanceof String) return attributeValue;
return attributeValue.toString();
} else if (type.equals("long")) {
if (attributeValue instanceof Long) return attributeValue;
if (attributeValue instanceof String) return
Long.valueOf((String)attributeValue);
throw new RuntimeException("cannot map type for token claim");
} else if (type.equals("int")) {
if (attributeValue instanceof Integer) return attributeValue;
if (attributeValue instanceof String) return
Integer.valueOf((String)attributeValue);
throw new RuntimeException("cannot map type for token claim");
}
return attributeValue;
The attribute exists with no value which causes the attrbuteValue to be
null and there is no check for null at that point. I would expect it would
return empty string if the type is string and the value is null.
Thanks,
jeff
8 years, 5 months
Re: [keycloak-user] Proxy configuration issue (Bill Burke)
by Adrian Matei
Hi Bill,
Thank your for your answer, but I still don't seem to get Keycloak to
"catch" my requests against the protected application.
Let me make the scenario clear:
1. Application to be protected runs on http://localhost:*8280*/backend
2. Server proxy started and runs on http://localhost:*8080*, when I type
http://localhost:8080/backend in the browser I see the protected application
3. Keycloak server runs on http://localhost:*8180*/auth
4. The adapter config in the "applications" section corresponds now the
proxy client I have configured in the Keycloak realm:
Client ID: proxy
Client Protocol: openid-connect
Access Type: confidential
Valid Redirect URIs: http://localhost:8080/backend/*
I am not sure how to configure the proxy Server - now I have the following:
{
"target-url": "*http://localhost:8280/ <http://localhost:8280/>*", ???
"send-access-token": false,
"bind-address": "localhost",
"http-port": "8080", ???
"applications": [
{
"base-path": "*/backend*",
"error-page": "/error.html",
"adapter-config": {
"realm": "demo",
"resource": "*proxy*",
"realm-public-key":
"MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrVrCuTtArbgaZzL1hvh0xtL5mc7o0NqPVnYXkLvgcwiC3BjLGw1tGEGoJaXDuSaRllobm53JBhjx33UNv+5z/UMG4kytBWxheNVKnL6GgqlNabMaFfPLPCF8kAgKnsi79NMo+n6KnSY8YeUmec/p2vjO2NjsSAVcWEQMVhJ31LwIDAQAB",
"auth-server-url": "http://localhost:8180/auth",
"ssl-required" : "external",
"principal-attribute": "name",
"credentials": {
"secret": "4ef4196d-9e86-4795-9219-dc1288b87c2b"
}
}
}
]
}
Questions:
1. The target-url I set it to the URL of the application the proxy server
is proxying - this means the server can only proxy applications on the same
URL?
2. What am I doing wrong :((((?
Thanks a bunch,
Adrian
"Can't really see the screenshot, but you have to point keycloak to the
host/port of the proxy.
On 11/19/2015 9:13 AM, Adrian Matei wrote:
> Hi everyone,
>
> I am trying to make a simple test and configure a keycloak proxy to
> protect an application running on http://localhost:8280/backend/
> >on looks like the following:
> >
> > {
> > "target-url": "http://localhost:8280/",
> > "send-access-token": false,
> > "bind-address": "localhost",
> > "http-port": "8080",
> > "applications": [
> > {
> > "base-path": "/backend",
> > "error-page": "/error.html",
> > "adapter-config": {
> > "realm": "demo",
> > "resource": "sandbox-backend",
> > "realm-public-key":
> >
> "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrVrCuTtArbgaZzL1hvh0xtL5mc7o0NqPVnYXkLvgcwiC3BjLGw1tGEGoJaXDuSaRllobm53JBhjx33UNv+5z/UMG4kytBWxheNVKnL6GgqlNabMaFfPLPCF8kAgKnsi79NMo+n6KnSY8YeUmec/p2vjO2NjsSAVcWEQMVhJ31LwIDAQAB",
> > "auth-server-url": "http://localhost:8180/auth",
> > "ssl-required" : "external",
> > "credentials": {
> > "secret": "9323cdd6-7e0e-46ce-814f-b5ac79581395"
> > }
> > }
> > }
> > ]
> > }
> >
> > 2.
> > I've started the proxy server as specified in the documentation "java
> > -jar bin/launcher.jar proxy.json"
> > I am getting an error "ERROR: UT005026: Jetty ALPN support not found on
> > boot class path, SPDY client will not be available.", but the server
> > still starts, I don't think there should be a problem with that...
> >
> > 3. In the admin console (keycloak running on port 8180) I've configured
> > the backend application like the following:
> >
> > Could you tell me what I am doing wrong? When I put in the app's url in
> > the browser it goes directly to the application...
> >
> > Thanks,
> > Adrian"
8 years, 5 months
Best practice: Server to Server authentication
by Kevin Hirschmann
Hello,
has anyone experience or advice how to handle the following situation:
I have my application running on a keycloak secured wildfly instance.
Another application
wants to make REST calls from an IIS Server to my application. Of course
the user is not
willing to provide credentials a second time, but the calls must be
associated with the user.
It must not be a shared account in keycloak, which is used for all users on
the IIS.
What is the right way (keycloak way) to approach this?
Thx for your help.
Kevin Hirschmann
HUEBINET Informationsmanagement GmbH & Co. KG
HUEBINET Informationsmanagement GmbH & Co. KG
An der Königsbach 8
56075 Koblenz
Sitz und Registergericht: Koblenz HRA 5329
Persönlich haftender Gesellschafter der KG:
HUEBINET GmbH;
Sitz und Registergericht: Koblenz HRB 6857
Geschäftsführung:
Frank Hüttmann; Michael Biemer
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------
Der Nachrichtenaustausch mit HUEBINET Informationsmanagement GmbH & Co. KG,
Koblenz via E-Mail dient lediglich zu Informationszwecken.
Rechtsgeschäftliche Erklärungen mit verbindlichem Inhalt können über dieses
Medium nicht ausgetauscht werden, da die Manipulation von E-Mails durch
Dritte nicht ausgeschlossen werden kann.
Email communication with HUEBINET Informationsmanagement GmbH & Co. KG is
only intended to provide information of a general kind, and shall not be
used for any statement with binding contents in respect to legal relations.
It is not totally possible to prevent a third party from manipulating emails
and email contents.
8 years, 5 months
Can I apply SSO using key cloak for different application
by Ismail Shaik
Hi
This is Ismail , I want to use SSO mechanism to apply for different
applications which are running on different web applications
for example one python and angular application is running on Ngenix web
server and and other applications running on Jboss . Can I configure the
python application on key cloak so that I can use the same credentials from
my LDAP ?
Please let know , appreciate your responses.
--
Thanks,
Ismail Shaik - 908 922 9571
8 years, 5 months
Database war is not deployable on Jboss EAP 6.2 with 1.1.0.Final version
by Ismail Shaik
Hi All,
I am trying the version 1.1.0 final with EAP 6.2 I am able to configure the
applications and users and roles with demo realm.
But some how database application is not deployable in Jboss EAP 6.2
I am getting the following issue when I try to login in demo realm to
access the customer-portal
session of subresource org.keycloak.protocol.oidc.OpenIDConnectService will
not be injected according to spec
while deploying in jboss with command mvn jboss-as:deploy is having the
below stack trace in my server
14:58:22,857 INFO [org.jboss.as.server.deployment] (MSC service thread
1-3) JBAS015876: Starting deployment of "database.war" (runtime-name:
"database.war")
14:58:22,888 INFO [org.jboss.web] (ServerService Thread Pool -- 61)
JBAS018210: Register web context: /database
14:58:22,892 ERROR [org.apache.catalina.startup] (ServerService Thread Pool
-- 61) JBWEB001034: Cannot configure an authenticator for method KEYCLOAK
14:58:22,893 ERROR [org.jboss.web] (ServerService Thread Pool -- 61)
JBAS018206: Webapp [/database] is unavailable due to startup errors
14:58:22,893 ERROR [org.apache.catalina.core] (ServerService Thread Pool --
61) JBWEB001103: Error detected during context /database start, will stop it
14:58:22,896 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool
-- 61) MSC000001: Failed to start service
jboss.web.deployment.default-host./database:
org.jboss.msc.service.StartException in service
jboss.web.deployment.default-host./database:
org.jboss.msc.service.StartException in anonymous service: JBAS018040:
Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService$1.run(
WebDeploymentService.java:96)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[rt.jar:1.7.0_75]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
[rt.jar:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: org.jboss.msc.service.StartException in anonymous service:
JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.doStart(
WebDeploymentService.java:161)
at org.jboss.as.web.deployment.WebDeploymentService.access$000(
WebDeploymentService.java:60)
at org.jboss.as.web.deployment.WebDeploymentService$1.run(
WebDeploymentService.java:93)
... 6 more
14:58:23,109 ERROR [org.jboss.as.server] (management-handler-thread - 6)
JBAS015870: Deploy of deployment "database.war" was rolled back with the
following failure message:
{"JBAS014671: Failed services" =>
{"jboss.web.deployment.default-host./database" => "
org.jboss.msc.service.StartException in service
jboss.web.deployment.default-host./database:
org.jboss.msc.service.StartException in anonymous service: JBAS018040:
Failed to start context
Caused by: org.jboss.msc.service.StartException in anonymous service:
JBAS018040: Failed to start context"}}
Can you please me with that, I am not able to login in demo with the create
roles . Thanks,
Ismail
--
Thanks,
Ismail Shaik - 908 922 9571
8 years, 5 months
keycloak-overlay-eap6-1.6.1.Final has jobs start up issue
by Ismail Shaik
Hi,
This is Ismail , I am trying to set up SSO using the key cloak , I
extracted the a *keycloak-overlay-eap6-1.6.1.Final *to my Jboss Home
which has the version 6.2.3. EAP and when I try to start the server I am
getting the below exception
se configuration
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141)
[jboss-as-controller-7.3.3.Final-redhat-SNAPSHOT.jar:7.3.3.Final-redhat-SNAPSHOT]
at org.jboss.as.server.ServerService.boot(ServerService.java:324)
[jboss-as-server-7.3.3.Final-redhat-SNAPSHOT.jar:7.3.3.Final-redhat-SNAPSHOT]
at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253)
[jboss-as-controller-7.3.3.Final-redhat-SNAPSHOT.jar:7.3.3.Final-redhat-SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[2,1]
Message: Unexpected element '{urn:jboss:domain:1.7}server'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
[staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
[staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133)
[jboss-as-controller-7.3.3.Final-redhat-SNAPSHOT.jar:7.3.3.Final-redhat-SNAPSHOT]
... 3 more
09:27:24,775 FATAL [org.jboss.as.server] (Controller Boot Thread)
JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See
previous messages for details.
09:27:24,784 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015950:
JBoss EAP 6.2.3.GA <http://6.2.3.ga/> (AS 7.3.3.Final-redhat-SNAPSHOT)
stopped in 4ms
I am running the server using below command.
bash standalone.sh --server-config=standalone-keycloak.xml
I am using the MAC OS
--
Thanks,
Ismail Shaik - 908 922 9571
8 years, 5 months
Users losing realm roles without a valid reason
by Johan Heylen
Hallo,
we have noticed a strange behaviour in our Keycloak setup:
After a while, some users lose one of their assigned realm roles, without
anyone actually requesting this from the keycloak server (We see no admin
events who can explain this behaviour).
Could it be that something is wrong in some cache implementation or an in
issue in concurrency?
When I make a dump of the database, the role can also no longer be found
there in the user export, so it actually gets removed from there as well.
One specific thing we do, is managing the realm settings using the admin
REST API, which PUTs the realm config JSON every X minutes (X is currently
5 to 2 minutes), so the PUT call happens a lot (I can see it in the admin
events).
To exclude this as possible culprit, I've disable this constant updating of
the realm. I'll send an update wether this has had any impact, but either
way, the issue should not occur.
Has anyone already encountered this issue?
I can provide you with more config of the keycloak server and realm if
required... We are one 1.6.0
Could you help me with enabling the correct logging, so I might be able to
trace where the problem occurs or see what causes the drop of a realm role
on a user (His other realms roles remain untouched...)
Currently I am not able to reproduce this with a testcase, it just occurs
from time to time on a test platform, so I did not create a JIRA ticket yet
Tnx,
Johan Heylen
DNS Belgium
8 years, 5 months
Cannot configure an authenticator for method KEYCLOAK
by Ataraxus
Hello,
having trouble to get my or the example app "customer-portal" working
with keycloak... I installed keycloak 1.6.1 on an EAP 6.4 via the
overlay and followed the youtube tutorials. Is there anything else i
have to configure, so that jboss finds the authenticator KEYCLOAK. The
apps are deployed on the
11:38:38,317 INFO [org.jboss.web] (ServerService Thread Pool -- 57)
JBAS018210: Register web context: /customer-portal
11:38:38,332 ERROR [org.apache.catalina.startup] (ServerService Thread
Pool -- 57) JBWEB001034: Cannot configure an authenticator for method
KEYCLOAK
11:38:38,332 ERROR [org.jboss.web] (ServerService Thread Pool -- 57)
JBAS018206: Webapp [/customer-portal] is unavailable due to startup errors
11:38:38,333 ERROR [org.apache.catalina.core] (ServerService Thread Pool
-- 57) JBWEB001103: Error detected during context /customer-portal
start, will stop it
11:38:38,365 ERROR [org.jboss.msc.service.fail] (ServerService Thread
Pool -- 57) MSC000001: Failed to start service
jboss.web.deployment.default-host./customer-portal:
org.jboss.msc.service.StartException in service
jboss.web.deployment.default-host./customer-portal:
org.jboss.msc.service.StartException in anonymous service: JBAS018040:
Failed to start context
at
org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:99)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[rt.jar:1.7.0_85]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
[rt.jar:1.7.0_85]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_85]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_85]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
Caused by: org.jboss.msc.service.StartException in anonymous service:
JBAS018040: Failed to start context
at
org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:168)
at
org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61)
at
org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96)
... 6 more
11:38:38,372 ERROR [org.jboss.as.controller.management-operation]
(HttpManagementService-threads - 3) JBAS014612: Operation ("add") failed
- address: ([{"deployment" => "customer-portal.war"}]) - failure
description: {"JBAS014671: Failed services" =>
{"jboss.web.deployment.default-host./customer-portal" =>
"org.jboss.msc.service.StartException in service
jboss.web.deployment.default-host./customer-portal:
org.jboss.msc.service.StartException in anonymous service: JBAS018040:
Failed to start context
Caused by: org.jboss.msc.service.StartException in anonymous
service: JBAS018040: Failed to start context"}}
11:38:38,385 ERROR [org.jboss.as.server] (HttpManagementService-threads
- 3) JBAS015870: Deploy of deployment "customer-portal.war" was rolled
back with the following failure message:
{"JBAS014671: Failed services" =>
{"jboss.web.deployment.default-host./customer-portal" =>
"org.jboss.msc.service.StartException in service
jboss.web.deployment.default-host./customer-portal:
org.jboss.msc.service.StartException in anonymous service: JBAS018040:
Failed to start context
Caused by: org.jboss.msc.service.StartException in anonymous
service: JBAS018040: Failed to start context"}}
11:38:38,399 INFO [org.jboss.as.server.deployment] (MSC service thread
1-2) JBAS015877: Stopped deployment customer-portal.war (runtime-name:
customer-portal.war) in 21ms
11:38:38,401 INFO [org.jboss.as.controller]
(HttpManagementService-threads - 3) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service
jboss.deployment.unit."customer-portal.war".component."com.sun.faces.config.ConfigureListener".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service
jboss.deployment.unit."customer-portal.war".component."javax.faces.webapp.FacetTag".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service
jboss.deployment.unit."customer-portal.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service
jboss.deployment.unit."customer-portal.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service
jboss.deployment.unit."customer-portal.war".component."org.apache.catalina.servlets.DefaultServlet".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service
jboss.deployment.unit."customer-portal.war".component."org.apache.jasper.servlet.JspServlet".START
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service jboss.web.deployment.default-host./customer-portal
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
service jboss.web.deployment.default-host./customer-portal.realm
(missing) dependents: [service
jboss.deployment.unit."customer-portal.war".deploymentCompleteService]
JBAS014777: Services which failed to start: service
jboss.web.deployment.default-host./customer-portal
8 years, 5 months
direct grant access with Resource Owner Password Credentials
by Ken Kong
I have setup the realms, the client and the users.
When I posted the request to
/auth/realms/{clientid}/protocol/openid-connect/token with client Id,
username, password and grant_type by SoapUI, I received error
{
"error_description": "Account is not fully set up",
"error": "invalid_grant"
}
The keycloak server is running on EAP-6.4.0
Below is the server stack trace
12:54:47,234 WARN [org.keycloak.events] (http-/127.0.0.1:8180-6)
type=LOGIN_ERROR, realmId=master, clientId=security-admin-console,
userId=null, ipAddress=127.0.0.1, error=resolve_required_actions,
auth_method=openid-connect, response_type=token,
client_auth_method=client-secret, username=kenk
12:54:47,235 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n]
(http-/127.0.0.1:8180-6) RESTEASY000105: Failed to execute:
org.keycloak.services.ErrorResponseException
at
org.keycloak.protocol.oidc.endpoints.TokenEndpoint.buildResourceOwnerPas
swordCredentialsGrant(TokenEndpoint.java:363)
[keycloak-services-1.6.1.Final.jar:1.6.1.Final]
at
org.keycloak.protocol.oidc.endpoints.TokenEndpoint.build(TokenEndpoint.j
ava:110) [keycloak-services-1.6.1.Final.jar:1.6.1.Final]
at sun.reflect.GeneratedMethodAccessor221.invoke(Unknown Source)
[:1.8.0_45]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:43) [rt.jar:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)
[rt.jar:1.8.0_45]
at
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.jav
a:168) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.jav
a:269) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceLocator.invokeOnTargetObject(ResourceLoc
ator.java:158) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceLocator.invoke(ResourceLocator.java:106)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceLocator.invokeOnTargetObject(ResourceLoc
ator.java:153) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.ResourceLocator.invoke(ResourceLocator.java:91)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDis
patcher.java:541) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatch
er.java:523) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatch
er.java:125) [resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.ser
vice(ServletContainerDispatcher.java:208)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(
HttpServletDispatcher.java:55)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(
HttpServletDispatcher.java:50)
[resteasy-jaxrs-2.3.10.Final-redhat-1.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-
2]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:295)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:214)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.keycloak.services.filters.KeycloakSessionServletFilter.doFilter(Keyc
loakSessionServletFilter.java:61)
[keycloak-services-1.6.1.Final.jar:1.6.1.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:246)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:214)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:231) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:149) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(Securit
yContextAssociationValve.java:169)
[jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:150) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:97) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:102) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
44) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:85
4) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:653)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926)
[jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
Regards,
KK
8 years, 5 months