9:35 a.m.
We have REST services on EAP 6.3.2 with adapter 1.3.1 and gateway server
WF 8.2 with 1.3.1 server. This configuration doesn't work. Our test case
works on WF 8.2 server with adapter 1.3.1.
Does anybody has idea, why it shouldn't work also with EAP 6.3.2? Are
there any incompatibilities?
--
*Mitja*
9:06 a.m.
EAP 6.3.2 should work just fine, but there's a separate adapter for EAP 6.3.
On 29 December 2015 at 16:35, Mitja Strojanšek <mitja.strojansek(a)efos.si>
wrote:
We have REST services on EAP 6.3.2 with adapter 1.3.1 and gateway
server
WF 8.2 with 1.3.1 server. This configuration doesn't work. Our test case
works on WF 8.2 server with adapter 1.3.1.
Does anybody has idea, why it shouldn't work also with EAP 6.3.2? Are
there any incompatibilities?
--
*Mitja*
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
6:53 a.m.
We have correct adapter.
The solution is to add @SecurityDomain("keycloak") to the service and
add <security-constraint> with <auth-constraint> to the web.xml.
Thx
--
*Mitja*
On 4.1.2016 16:06, Stian Thorgersen wrote:
EAP 6.3.2 should work just fine, but there's a separate adapter
for
EAP 6.3.
On 29 December 2015 at 16:35, Mitja Strojanšek
<mitja.strojansek(a)efos.si <mailto:mitja.strojansek@efos.si>> wrote:
We have REST services on EAP 6.3.2 with adapter 1.3.1 and gateway
server WF 8.2 with 1.3.1 server. This configuration doesn't work.
Our test case works on WF 8.2 server with adapter 1.3.1.
Does anybody has idea, why it shouldn't work also with EAP 6.3.2?
Are there any incompatibilities?
--
*Mitja*
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user
3160
days inactive
3175
days old
2 comments
2 participants
participants (2)
-
Mitja Strojanšek -
Stian Thorgersen