Custom log in on 11g

Question

I have used Configure ADF Security Wizard to cofigure web.xml, jsp-config.xml, jazn-data.xml.....
Then I have changed jsp-confing.xml and in Login Modules section I have added customLogin -
code:
<serviceInstance name="customLogin" provider="jaas.login.provider">
<property value="theNameOfMyClass" name="loginModuleClassName"/>
<property name="jaas.login.controlFlag" value="REQUIRED"/>
<property name="debug" value="true"/>
<property name="addAllRoles" value="true"/>
<property name="someproperty" value="somevalue"/>.....
<property name="log.level" value="FINEST"/>
</serviceInstance>
then I have changed properties for default security context to look like:
<jpsContexts default="NAME">
<jpsContext name="NAME">
<serviceInstanceRef ref="credstore"/>
<serviceInstanceRef ref="customLogin"/>
<serviceInstanceRef ref="anonymous"/>
<serviceInstanceRef ref="policystore.xml"/>
<serviceInstanceRef ref="idstore.xml"/>
</jpsContext>
<jpsContext name="anonymous">
<serviceInstanceRef ref="credstore"/>
<serviceInstanceRef ref="anonymous"/>
<serviceInstanceRef ref="anonymous.loginmodule"/>
</jpsContext>
</jpsContexts>
First I have tested my customLogin on application module changing "jbo.security.enforce" to "Auth" and setting "jbo.security.logingmodule" to "customLogin" and it worked just fine.
Then I defined some rules for accessing pages in jazn-data.xml based on roles that have the same name as roles defined in database (because my customLogin (class that implements LoginModule) actually go to data base and checked for right username and password )....and nothing ....it seams that my customLogin isn't triggered at all. What am I missing?

Answer 1

Hi,
unless you are on a Technology Preview build, the following has changed in JDeveloper 11 production
- custom LogiNModules are no longer configured in jps-config. Instead they need to be defined as authentication providers in WLS. This is supposed to change to the better in a future release, but for now its the way it is.
- jbo.security.enforce" to "Auth" is no longer used when ADF Security is enabled. The configuration is read from the adf-config.xml file in the .adf\META-INF directory
You may want to have a look at the recodings posted here
http://www.oracle.com/technology/products/jdev/tips/fnimphius/
Frank