Skip to main content

*** NOT ADF - Glassfish custom login module

Step 1) Write your custom module - there are enough examples out there - I used (http://x-techteam.blogspot.com/2008/03/glassfish-login-module-simple-example.html)
Step 2) Add to login.conf [glassfish location]\glassfish\domains\[domain name]\config
yourRealm{
    za.co.jaas.realm.YourLoginModule required;
};

Step 3) Admin console setup
  • Goto admin console : http://localhost:4848 and Login
  • Goto Cconfigurations\[Your config]\Security\Realms
  • Click new button
  • ClassName: za.co.jaas.realm.YourRealm (choose second custom radio button)
  • Name:     yourRealm
  • Press the ok button
BIG BIG NOTE: (Save yourself hours of time)
Tick Default Principal To Role Mapping in configurations\[Your config]\Security\ and save
stop glassfish
REDEPLOY APPLICATION
start glasfish

NOTE : When writing a startup script please remeber to start db before start of Assfish otherwise you will have some strange funky errors.
Labels:

Comments

  1. hvJuly 22, 2011 at 3:04 PM

    I recommend to package and deploy the CustomRealm as an OSGi module. See http://stackoverflow.com/questions/4526674/custom-glassfish-security-realm-does-not-work-unable-to-find-loginmodule for details.

    ReplyDelete
  2. Donovan SherriffsJuly 23, 2011 at 3:54 AM

    Spot on, Thanks will make it so

    ReplyDelete

Post a Comment

Popular posts from this blog

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]
1 comment
Read more

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop...
Post a Comment
Read more

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    
3 comments
Read more