blob: b31f7e686c326296684846e24a270b8ac8d53c6f [file] [log] [blame]
= Security Annotations
:index-group: Unrevised
:jbake-date: 2018-12-05
:jbake-type: page
:jbake-status: published
This page shows the correct usage of the security
related annotations:
* javax.annotation.security.RolesAllowed
* javax.annotation.security.PermitAll
* javax.annotation.security.DenyAll
* javax.annotation.security.RunAs
* javax.annotation.security.DeclareRoles
== Basic idea
* By default all methods of a business interface are accessible, logged
in or not
* The annotations go on the bean class, not the business interface
* Security annotations can be applied to entire class and/or individual
methods
* The names of any security roles used must be declared via
@DeclareRoles
== No restrictions
Allow anyone logged in or not to invoke 'svnCheckout'.
These three examples are all equivalent.
[source,java]
----
@Stateless
public class OpenSourceProjectBean implements Project {
public String svnCheckout(String s) {
return s;
}
}
@Stateless
@PermitAll
public class OpenSourceProjectBean implements Project {
public String svnCheckout(String s) {
return s;
}
}
@Stateless
public class OpenSourceProjectBean implements Project {
@PermitAll
public String svnCheckout(String s) {
return s;
}
}
----
* Allow anyone logged in or not to invoke 'svnCheckout'.
== Restricting a Method
Restrict the 'svnCommit' method to only individuals logged in and part
of the "committer" role. Note that more than one role can be listed.
[source,java]
----
@Stateless
@DeclareRoles({"committer"})
public class OpenSourceProjectBean implements Project {
@RolesAllowed({"committer"})
public String svnCommit(String s) {
return s;
}
public String svnCheckout(String s) {
return s;
}
}
----
* Allow only logged in users in the "committer" role to invoke
'svnCommit'.
* Allow anyone logged in or not to invoke 'svnCheckout'.
== DeclareRoles
You need to update the `@DeclareRoles` when referencing roles via
isCallerInRole(roleName).
[source,java]
----
@Stateless
@DeclareRoles({"committer", "contributor"})
public class OpenSourceProjectBean implements Project {
@Resource SessionContext ctx;
@RolesAllowed({"committer"})
public String svnCommit(String s) {
ctx.isCallerInRole("committer"); // Referencing a Role
return s;
}
@RolesAllowed({"contributor"})
public String submitPatch(String s) {
return s;
}
}
----
== Restricting all methods in a class
Placing the annotation at the class level changes the default of
PermitAll
[source,java]
----
@Stateless
@DeclareRoles({"committer"})
@RolesAllowed({"committer"})
public class OpenSourceProjectBean implements Project {
public String svnCommit(String s) {
return s;
}
public String svnCheckout(String s) {
return s;
}
public String submitPatch(String s) {
return s;
}
}
----
* Allow only logged in users in the "committer" role to invoke
'svnCommit', 'svnCheckout' or 'submitPatch'.
== Mixing class and method level restrictions
Security annotations can be used at the class level and method level at
the same time. These rules do not stack, so marking 'submitPatch'
overrides the default of "committers".
[source,java]
----
@Stateless
@DeclareRoles({"committer", "contributor"})
@RolesAllowed({"committer"})
public class OpenSourceProjectBean implements Project {
public String svnCommit(String s) {
return s;
}
public String svnCheckout(String s) {
return s;
}
@RolesAllowed({"contributor"})
public String submitPatch(String s) {
return s;
}
}
----
* Allow only logged in users in the "committer" role to invoke
'svnCommit' or 'svnCheckout'
* Allow only logged in users in the "contributor" role to invoke
'submitPatch'.
== PermitAll
When annotating a bean class with `@RolesAllowed`, the `@PermitAll`
annotation becomes very useful on individual methods to open them back
up again.
[source,java]
----
@Stateless
@DeclareRoles({"committer", "contributor"})
@RolesAllowed({"committer"})
public class OpenSourceProjectBean implements Project {
public String svnCommit(String s) {
return s;
}
@PermitAll
public String svnCheckout(String s) {
return s;
}
@RolesAllowed({"contributor"})
public String submitPatch(String s) {
return s;
}
}
----
* Allow only logged in users in the "committer" role to invoke
'svnCommit'.
* Allow only logged in users in the "contributor" role to invoke
'submitPatch'.
* Allow anyone logged in or not to invoke 'svnCheckout'.
== DenyAll
The `@DenyAll` annotation can be used to restrict business interface
access from anyone, logged in or not. The method is still invokable from
within the bean class itself.
[source,java]
----
@Stateless
@DeclareRoles({"committer", "contributor"})
@RolesAllowed({"committer"})
public class OpenSourceProjectBean implements Project {
public String svnCommit(String s) {
return s;
}
@PermitAll
public String svnCheckout(String s) {
return s;
}
@RolesAllowed({"contributor"})
public String submitPatch(String s) {
return s;
}
@DenyAll
public String deleteProject(String s) {
return s;
}
}
----
* Allow only logged in users in the "committer" role to invoke
'svnCommit'.
* Allow only logged in users in the "contributor" role to invoke
'submitPatch'.
* Allow anyone logged in or not to invoke 'svnCheckout'.
* Allow _no one_ logged in or not to invoke 'deleteProject'.
= Illegal Usage
Generally, security restrictions cannot be made on AroundInvoke methods
and most callbacks.
The following usages of `@RolesAllowed` have no effect.
[source,java]
----
@Stateful
@DecalredRoles({"committer"})
public class MyStatefulBean implements MyBusinessInterface {
@PostConstruct
@RolesAllowed({"committer"})
public void constructed(){
}
@PreDestroy
@RolesAllowed({"committer"})
public void destroy(){
}
@AroundInvoke
@RolesAllowed({"committer"})
public Object invoke(InvocationContext invocationContext) throws
----
Exception \{ return invocationContext.proceed(); }
[source,java]
----
@PostActivate
@RolesAllowed({"committer"})
public void activated(){
}
@PrePassivate
@RolesAllowed({"committer"})
public void passivate(){
}
}
----