If the two apply to the same web resource collection and http method, will all the roles allowed to access or no roles allowed to access?
I think that no user is allowed to access, since the spec says: "The special case of an authorization constraint that names no roles shall combine with any other constraints to override their affects and cause access to be precluded."
Here is another one, the combination of <auth-constraint/> with no <auth-constraint>.
The spec and HFSJ both mentioned the combination of <auth-constraint/> with others and empty <auth-constraint> with others, but didn't mention which wins when these two are combined.
I tested in tomcat 5.5, the result is that the request is allowed without authentication.
Anyone can confirm this is the behaviour of the spec? Did I miss something form the spec?
posted 8 years ago
Sorry, when I say "empty <auth-constraint>" I mean there is no <auth-constraint> in a <security-constraint>.
I also tested <auth-constraint/> with <auth-constraint>*</auth-constraint> combination, the result is that the request is refused after .authentication. So NO <auth-constraint> is not equivalent to <auth-constraint>*</auth-constraint> when combined to <auth-constraint/>.
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads