I wonder what this infamous "Vignette HTTP 403 status problem" is?
My guess would be that Vignette's HTTP 403 response status means exactly the same as any other web server's HTTP 403 response status, i.e. you don't have the required privileges to access the resource you're trying to access.
hi please read this document you can find solution...
the Portal Portlet Packaging Tool adds a security filter to a portlet application’s web.xml file. This filter allows direct requests to static files, such as images, but it blocks all requests to servlets and JSPs that are not proxied through Portal, thereby ensuring that the Portal authentication and authorization mechanisms protect all application resources. As a result, a Portal user is forbidden to access a portlet application directly. Hwoever, we need to make direct requests to the FileExplorerServlet. To enable access we will remove the Portal security filter (named PortletApplicationSecurityFilter) and the mapping. Delete or comment the following lines: