• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

doubt in auth-constraint

 
V Gala
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
which option is valid?
A)

<auth-constraint>
<role-name>Bob</role-name>
</auth-constraint>
<auth-constraint>
<role-name>Alice</role-name>
</auth-constraint>


B)
<auth-constraint>
<role-name>Bob</role-name>
<role-name>Alice</role-name>
</auth-constraint>
 
Reesha Ashok
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
B.In a <security-constraint> tag, only one <auth-constraint> is allowed. It can have multiple roles.
 
V Gala
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But in errata page they have made changes like option a (page 662)
 
Christophe Verré
Sheriff
Posts: 14691
16
Eclipse IDE Ubuntu VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But in errata page they have made changes like option a (page 662)

Is option "a" given as a right answer in the book ? (it's not written in the errata)
[ April 09, 2008: Message edited by: Christophe Verre ]
 
Reesha Ashok
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by V Gala:
But in errata page they have made changes like option a (page 662)


Errata in page 662 doesn't mention about the answer options. It's about the question. It mentions the code was given in a wrong way. The auth-constraint elements which had 'Bob' and 'Alice' didn't have the <role-name> tag inside the <auth-constraint> which was corrected in the errata.
In the question it's mentioned that each of these <auth-constraint> tags belong to three valid <security-constraint> elements in a deployment descriptor.
 
V Gala
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks
I got it
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic