libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

KEYCLOAK-5665 - elytron propagate security domain to ejb

Browse source
This commit is contained in:
slominskir 2019-04-03 13:48:12 -04:00 committed by Marek Posolda
parent 02fb7958ea
commit 7f40c21851
2 changed files with 2 additions and 57 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
securing_apps/topics/oidc/java/jboss-adapter.adoc
View file

@ -292,22 +292,4 @@ If you have multiple deployments secured by the same realm you can share the rea
===== Security Domain ===== Security Domain
To propagate the security context to the EJB tier you need to configure it to use the "keycloak" security domain. This The security context is propagated to the EJB tier automatically.
can be achieved with the @SecurityDomain annotation:
[source,java]
----
import org.jboss.ejb3.annotation.SecurityDomain;
...
@Stateless
@SecurityDomain("keycloak")
public class CustomerService {
@RolesAllowed("user")
public List<String> getCustomers() {
return db.getCustomers();
}
}
----

39
securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc
View file

@ -136,44 +136,7 @@ Otherwise this configuration is optional.
</security-domains> </security-domains>
---- ----
For example, if you have a JAX-RS service that is an EJB within your WEB-INF/classes directory, The security context is propagated to the EJB tier automatically.
you'll want to annotate it with the `@SecurityDomain` annotation as follows:
[source,java]
----
import org.jboss.ejb3.annotation.SecurityDomain;
import org.jboss.resteasy.annotations.cache.NoCache;
import javax.annotation.security.RolesAllowed;
import javax.ejb.EJB;
import javax.ejb.Stateless;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import java.util.ArrayList;
import java.util.List;
@Path("customers")
@Stateless
@SecurityDomain("keycloak")
public class CustomerService {
@EJB
CustomerDB db;
@GET
@Produces("application/json")
@NoCache
@RolesAllowed("db_user")
public List<String> getCustomers() {
return db.getCustomers();
}
}
----
We hope to improve our integration in the future so that you don't have to specify the
`@SecurityDomain` annotation when you want to propagate a keycloak security context to the EJB tier.
===== JBoss SSO ===== JBoss SSO