I have the following navigation case:
<navigation-case>
<from-outcome>nav_page_domain_op_list</from-outcome>
<to-view-id>/page_domain_op_list</to-view-id>
</navigation-case>
and the following security constraint:
...
<url-pattern>/page_domain_op_list.jsf</url-pattern>
...
If I point my browser to localhost:8080/myapp/page_domain_op_list.jsf, the web app works fine and the sign-in page is popup up by the container automatically.
However I run into issues when I want to add same control on a JSF/Myfaces command link or command button. I tried to use "page_domain_op_list.jsf" or "nav_page_domain_op_list.jsf" as the action value, but neither worked.
How should I handle this kind of situation? Has anyone put any thoughts into this? I'd really appreciate your inputs.
Regards,
Ming
- Container managed authentication in Myfaces/JSF Ming Hu
- Re: Container managed authentication in Myfaces/J... Grigoras Cristinel
- Re: Container managed authentication in Myfac... Ming Hu
- Re: Container managed authentication in M... Craig McClanahan
- Re: Container managed authentication in M... Grigoras Cristinel
- AW: Container managed authentication ... Matthias Kahlau
- Re: Container managed authentication ... Ming Hu
- Re: Container managed authentica... Joey Geiger
- Re: Container managed authen... Andrew Robinson
- Migrating ADF Faces app ... Frank Felix Debatin
- Re: Migrating ADF Faces ... Rogers Reilly

