| Author |
Doubts: Mock by HFSJ 1st Edt
|
Poonam Agarwal
Ranch Hand
Joined: May 12, 2008
Posts: 323
|
|
Given that a deployment descriptor has only one security role, defined as:
<security-role>
<role-name>Member</role-name>
</security-role>
Which are valid <auth-constraint> elements that will allow users to
access resources constrained by the security role declared?
(Choose all that apply.)
A. <auth-constraint/>
B. <auth-constriant>*</auth-constraint>
C. <auth-constraint>Member</auth-constraint>D. <auth-constraint>MEMBER</auth-constraint>
E. <auth-constraint>”Member”</auth-constraint>
Given answers B, C
I am agree with the option C, but i haven't notive option B anywhere in the book. Is this gives the same effect if we say ???
<auth-constriant>
<role-name>*<role-name>
</auth-constraint>
Please correct me
|
Thanks <br />Poonam Agarwal SCWCD 86%
|
 |
Vishal Chugh
Ranch Hand
Joined: Oct 27, 2007
Posts: 177
|
|
No, its there in book with examples . I am in office , cant tell you page number sorry .
See * means all are allowed to access.
I also used to get confused , then i summerized in this
Hope , it will clear your doubt.
|
 |
Poonam Agarwal
Ranch Hand
Joined: May 12, 2008
Posts: 323
|
|
Thanks Vishal.
it has clear my doubt.. I will appreciate your effort if you can provide me the page no. in HFSJ showing use of the same.
Thanks
|
 |
Vishal Chugh
Ranch Hand
Joined: Oct 27, 2007
Posts: 177
|
|
Yes,
HFSJ 1st edition :
Page 637 : with heading : "The way <auth-constraint> works" has example of it with additional note at bottom of that page for wildcard character *
|
 |
Poonam Agarwal
Ranch Hand
Joined: May 12, 2008
Posts: 323
|
|
I got 2nd edition.
Its ok thank you very much for your concern
|
 |
 |
|
|
subject: Doubts: Mock by HFSJ 1st Edt
|
|
|