Databases
StackOverflow2013
Postsdbo
POServlet 3.0 odd declarative security behavior
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POServlet 3.0 odd declarative security behavior
    primarykey
    data
    text
    <p>I have a security constraint declared in web.xml:</p> <pre><code> &lt;security-constraint&gt; &lt;web-resource-collection&gt; &lt;web-resource-name&gt;LoggedIn&lt;/web-resource-name&gt; &lt;url-pattern&gt;/screens/*&lt;/url-pattern&gt; &lt;/web-resource-collection&gt; &lt;auth-constraint/&gt; &lt;user-data-constraint&gt; &lt;transport-guarantee&gt;CONFIDENTIAL&lt;/transport-guarantee&gt; &lt;/user-data-constraint&gt; &lt;/security-constraint&gt; </code></pre> <p>After logging in, when I make a GET request against the application I get the expected behavior e.g.</p> <p><code>https://localhost:8443/Patrac/screens/user.xhtml</code> --> results in access denied.</p> <p>However, when I do a postback e.g.</p> <p><code>&lt;rich:menuItem submitMode="ajax" label="User" action="/screens/user"/&gt;</code></p> <p>I can view the screen. If I do a second identical postback, I get the access denied message. Each time I submit a postback the result alternates between displaying the screen and issuing a 403. The URL displayed in the browser alternates between the following:</p> <p><code>https://localhost:8443/Patrac/screens/user.xhtml</code> --> browser URL when access denied </p> <p><code>https://localhost:8443/Patrac/public/403.xhtml</code> --> browser URL when user screen is displayed</p> <p>I understand the way the displayed browser URL in JSF lags behind the screen that is currently displayed, so that's no mystery. But I don't understand how I'm able to view the screen every other time the same postback is submitted. Again, GET requests are always denied.</p> <p><strong>EDIT :</strong></p> <p>I did try post-redirect-get and that made the strange behavior go away, as expected.</p> <pre><code>&lt;rich:menuItem submitMode="ajax" label="User" action="/screens/user?faces-redirect=true"/&gt; </code></pre> <p>However, I don't want to do PRG every time and besides PRG doesn't eliminate the security problem.</p> <p>What am I missing here? Thanks for any insights!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPatrick Garner
    1. USPatrick Garner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POServlet 3.0 odd declarative security behavior
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo at first you are accessing a resource in public directory and then doing a forward to screens and as expected it won't restrict that. But after that did you try to view the same view again I mean /public/ -> /screens/user.xhtml --> /screens/user.xhtml
      singulars
      1. POServlet 3.0 odd declarative security behavior
      1. USRavi
    2. COIt doesn't seem to matter whether I first view a screen in /public or not. If I try to view any of the screens under /screens (e.g. /screens/xxxx.xhtml) via postback I get the alternating behavior described above (back and forth between showing the screen and then issuing a 403). When I submit a GET the alternating behavior goes away.
      singulars
      1. POServlet 3.0 odd declarative security behavior
      1. USPatrick Garner
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload