@Documented
@Retention(value=RUNTIME)
public @interface HttpMethodConstraint
ServletSecurity
annotation to represent security constraints on specific
HTTP protocol messages.Modifier and Type | Required Element and Description |
---|---|
java.lang.String |
value
Http protocol method name
|
Modifier and Type | Optional Element and Description |
---|---|
ServletSecurity.EmptyRoleSemantic |
emptyRoleSemantic
The default authorization semantic.
|
java.lang.String[] |
rolesAllowed
The names of the authorized roles.
|
ServletSecurity.TransportGuarantee |
transportGuarantee
The data protection requirements (i.e., whether or not SSL/TLS is required) that must be satisfied by the connections
on which requests arrive.
|
public abstract java.lang.String value
value
may not be null, or the empty string, and must be a
legitimate HTTP Method name as defined by RFC 7231.public abstract ServletSecurity.EmptyRoleSemantic emptyRoleSemantic
rolesAllowed
returns a non-empty
array, and should not be specified when a non-empty array is specified for rolesAllowed.ServletSecurity.EmptyRoleSemantic
to be applied when rolesAllowed
returns an empty (that is,
zero-length) array.public abstract ServletSecurity.TransportGuarantee transportGuarantee
ServletSecurity.TransportGuarantee
indicating the data protection that must be provided by the connection.public abstract java.lang.String[] rolesAllowed
emptyRoleSemantic
. If emptyRoleSemantic
returns DENY, and
rolesAllowed
returns a zero length array, access is to be denied independent of authentication state and
identity. Conversely, if emptyRoleSemantic
returns PERMIT
, it indicates that access is to
be allowed independent of authentication state and identity. When the array contains the names of one or more roles,
it indicates that access is contingent on membership in at least one of the named roles (independent of the value
returned by emptyRoleSemantic
).