[JBoss Portal] - Help with portlet authentication
by dcollodel
Hi,
I am currently deploying Documentum portlets to Jboss portal. I've been successful in getting them to work with a separate login, but not using the Portal's security principal. The documentation is leaving me hanging on the Jboss configuration side, so any help would be greatly appreciated.
I've configured the portlet application on the backend for "trusted authentication", but it seems that the security principal is not being passed from Jboss to the WDK portlet applications.
The portlet documentation states:
anonymous wrote :
| Set up J2EE principals in the application deployment description web.xml and in application server-specific files...
|
| To set up J2EE principals:
| To enable J2EE principals to log in to repositories (single login), you must modify the deployment descriptor file (/WEB-INF/web.xml) and follow the procedures that are specific to your portal server.
|
| 1. In /WEB-INF/web.xml, remove the comments around the security constraints element. This sets up a user role called "Âeveryone"Â. The web-resource-name value should match the context name of the Web application. For example:
|
| | <security-constraint>
| | <web-resource-collection>
| | <web-resource-name></web-resource-name>
| | <url-pattern>/*</url-pattern>
| | <http-method>POST</http-method>
| | <http-method>GET</http-method>
| | </web-resource-collection>
| | <auth-constraint>
| | <role-name>everyone</role-name>
| | </auth-constraint>
| | </security-constraint>
| | <login-config>
| | <auth-method>BASIC</auth-method>
| | </login-config>
| |
|
| 2. Follow the portal server procedure for setting up J2EE principals. Each portal server has its own procedure for enabling single login.
For Step 1, it's referring to the web.xml of the Documentum portlets. I'm unsure what the context name should be.
Step 2 seems to be where the real trouble is though. If I can get J2EE principals set up, I think I can get the above XML correctly configured.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132622#4132622
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132622
16 years, 8 months
[EJB 3.0] - StackOverflowException caused by throwing app exception with
by LordCoven
Hi All,
Just had and resolved a really nasty problem. I've got a stateful (but I'd also tried the same with a stateless) EJB3 session bean which access an OpenLDAP backend to find some user data. I'm catching the NamingException when attempting the search and throwing my own application exception (UnableToQueryLdapException extends RuntimeException) with the NamingException added as the cause (i.e. super(e) in the constructor of the application exception).
I caused the search to fail by providing a bogus baseDN and in debugging was able to see the NamingException being caught and containing all the information I'd expect, but when I then threw it on as part of my application exception the app bombed out with a huge recursive stack trace to do with serialization.
When I changed the application exception to only take the message of the NamingException (e.getMessage()), the problem went away.
Sounds like it might be a nasty bug in the serialization code in JBoss?
I'm using JBoss 4.2.2.GA
The behaviour was tested on an XP box and an OS X 10.5.2 box both with JDK5.
Cheers,
Clive
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132618#4132618
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132618
16 years, 8 months