ADF Security in JDeveloper 10.1.3.4

Question

Hello all,
Although I have followed all the steps outlined in Ch. 30 Adding Security to an Application (ADF Dev Guide for Forms/4GL Developers) I cannot get ADF security running in JDev 10.1.3.4. Specifically,update, create and delete buttons are enabled even though I have put constraints on the respective iterator bindings. At the same time, i am not getting any errors.
Container managed security works fine and when I access a protected URL, the basic pop-up window shows (I am using basic authentication). The 4GL guide states the adfAuthenticationServlet should be mapped to its own URL pattern, like /adfAuthentication/*.
However, when I try to access an ADF protected resource, nothing happens.
What is the interaction between container managed security and the adfAuthentication servlet? is it mandatory to use a login page for the adfAuthentication servlet to work?
I understand a backing bean is needed if we want to make user information accessible in the expression language. However, according to table 30-1 (on pg. 30-24) no further action is needed in order for the, e.g. Create button to be disabled. In other words, a backing bean is not needed and I don't have to change the "disabled" property for the Create button from false and check it using EL.
COuld someoneplease shed some light how is ADF security actually used? Curiously enough, SRDemo is not using ADF security and I wonder why?
Many thanks,
Boris
Edited by: user616226 on Sep 12, 2008 2:53 PM

Answer 1

I made some progress. The missing link was running the ADF security wizard (under "Tools").
The buttons are behaving OK (rendered but disabled) but now no table data is displayed!?
I have granted a view permission on the binding container as well as a read permission on the iterator and attributes.
BTW, the ADF security wizard will create the adf-config file for you (had to be done manually, check pg. 30-25 in the 4GL guide).