The challenge is that pluto uses the underlying servlet container's
authentication. As you know, servlet auth requires a challenge/response
paradigm, and because of that, it's nearly impossible to have a login
that is not prompted by a request else.
If you're only looking to test portlets, try using the jsp/filter
approach to portlet deployment and configuring it to not be secure. You
can then hit the portal pages for auth.
Any other ideas would be welcome. . .
David
John Lewis wrote:
Any suggestions on how best to test portlets in Pluto Portal Driver
1.1.3+ without logging in? Obviously I can comment out the
<security-constraint> section in the web.xml and make everything work
anonymously, but it would be nice to have access to both authenticated
content and unauthenticated content without reconfiguring and restarting.
The ideal thing would be to have the unauthenticated page contain both
the login screen and anonymous portlets, and then have different content
once the user logs in. I know this would add some complexity to the
Portal Driver, but I think this is a valid and interesting testing
scenario.
