Security constraint problem with v4.1.18

[Peter Lee]

I upgraded from 4.1.12 to 4.1.18, but I got some problems with security constraints.
I have applied a security constraint on a particular url pattern. Only certain users 
with a special rolename can 
access that link. It used to work but now the page does not load with v4.1.18.
Is SSL implemented differently after v4.1.12 that prevents my application fromworking?

     <security-constraint>
    <web-resource-collection>
      <web-resource-name>SSLResource</web-resource-name>
      <url-pattern>/protected</url-pattern>
    </web-resource-collection>
    <auth-constraint>
      <role-name>myrole</role-name>
    </auth-constraint>
    <user-data-constraint>
      <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>
  </security-constraint>
 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>