Hi,
Afraid another question from me on XPages, may be something basic but I haven’t found the answer yet. I have made an application that in various places has a button that would open a different XPage (which is contained in the same application). The button (under onclick) has a ‘simple action’ set of ‘open page’.
But here’s the problem. If I preview the XPage in the browser (from the Designer client), everything works great (launches http). However, if I log in as an external user would (https), the button seems to fail. When you click the button, the page then becomes blank and doesn’t load the new XPage. Looking at the url it also doesn’t change as it should to the new url, it’s almost as if it gives up halfway.
The only thing that changes when logging in as an external user is that instead of running http, it runs https (SSL) forcing them to login with their internet certificate we provide them with.
Is there anything I need to change on the Xpages/application for it to work with https/SSL? I have signed the application in an Administration client with my ID (I am an administrator and have access to the server the application is running on) and I have also added my ID to ‘Sign or run unrestricted methods and operations:’ in the server document.
If I use a direct url link to the new XPage to load; it works strangely enough, so I didn’t think it was an application access problem when running HTTPS/SSL. Is there an execution access I have overlooked in the server document or some security I need to change on the new XPage itself?
Thanks in advance to anyone who suggests anything. I’ve completely hit a wall on this!
