[
https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys...
]
Pedro Igor edited comment on ELY-19 at 3/14/16 12:29 PM:
---------------------------------------------------------
[~darranl],
I think we can close this issue. The reason is that Keycloak integration is all about
implementing an authentication mechanism based on Elytron HTTP API.
Not sure if we really need a security realm for Keycloak, but maybe a different type of
realm that can deal with JWT tokens. I've already implemented an initial version of a
JWT-based realm, which uses a {{BearerTokenEvidence}} to pass the JWT to the security
realm and creates identities from it. Pretty much what we have in {{OAuth2SecurityRealm}},
but using JWTs instead of a JSON response from the token introspection endpoint.
Any thoughts ?
was (Author: pcraveiro):
[~darranl],
I think we can close this issue. The reason is that Keycloak integration is all about
implementing an authentication mechanism based on Elytron HTTP API.
Not sure if we really need a security realm for Keycloak, but maybe a different type of
realm that can deal with JWT tokens. I've already implemented an initial version of a
JWT-based realm, which uses a ```BearerTokenEvidence``` to pass the JWT to the security
realm and creates identities from it. Pretty much what we have in
```OAuth2SecurityRealm```, but using JWTs instead of a JSON response from the token
introspection endpoint.
Any thoughts ?
Add KeyCloak based realm implementation.
----------------------------------------
Key: ELY-19
URL:
https://issues.jboss.org/browse/ELY-19
Project: WildFly Elytron
Issue Type: Sub-task
Reporter: Darran Lofthouse
Assignee: Pedro Igor
Fix For: 1.1.0.CR1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)