Strange Region Permission error on table iterator

Question

Adf 11g
Hello
I have an unbounded task flow containing a page.
On this page there is a bounded task flow as a region.
The main page of the bounded task flow contains several panel collections,
each panel collection contains an af:table.
A select once choice has been put on the bounded task flow page for navigation
which via ppr refreshes the tables.
If I use the select one choice to navigate and the tables are empty no error occurs.
However if I use the select one choice to navigate and if any of the tables are not empty I get the
following error(s)) in the log - there is one error for each non empty table iterator.
[JpsAuth] Check Permission
          PolicyContext:        [trac#V2.0]
          Resource/Target:      [sessiondef.ui_pages_transaction_mainTransactionPageDef_SttTransactionSellView_0_DynamicRegion]
          Action:               [view]
          Permission Class:     [oracle.adf.share.security.authorization.RegionPermission]
          Result:               [FAILED]
          For more information on this failure, please set -Djps.auth.debug.enable=true
[JpsAuth] Check Permission
          PolicyContext:        [trac#V2.0]
          Resource/Target:      [sessiondef.ui_pages_transaction_mainTransactionPageDef_SttTransSellCollateralView_0_DynamicRegion]
          Action:               [view]
          Permission Class:     [oracle.adf.share.security.authorization.RegionPermission]
          Result:               [FAILED]
          For more information on this failure, please set -Djps.auth.debug.enable=true
[JpsAuth] Check Permission
          PolicyContext:        [trac#V2.0]
          Resource/Target:      [sessiondef.ui_pages_transaction_mainTransactionPageDef_SttTransactionBuyView_0_DynamicRegion]
          Action:               [view]
          Permission Class:     [oracle.adf.share.security.authorization.RegionPermission]
          Result:               [FAILED]
          For more information on this failure, please set -Djps.auth.debug.enable=trueThe application is secured by form based authentication.
The main page of the unbounded task flow has been granted the view option as
has the bounded task flow used as a region.
Can anybody explain these errors ?
Why is there a dynamic region mentioned for each iterator and why is the
system looking for a view grant on this (non existant) dynamic region ?
Where do I set the -Djps... option ?
Regards
Paul

Answer 1

Hi,
don't think it has directly to do with the iterator. My assumption is that each table is queried in its own request and therefore the authorization on the Pagedef file is tested as many times. All of them fail, which is odd since they are in a bounded task flow and should not be security checked. Did you apply security to the page in the bounded task flow (its not necessary). Is the page built on a page template that provides the binding for the table ? If so then the pageDef file of the template needs to be secured as well
Frank