Title | | » | Skyline assumes /labkey context path when pinging Panorama |
Assigned To | Guest | » | Vagisha |
Type | | » | Defect |
Area | | » | Skyline |
Priority | | » | 3 |
Milestone | | » | 4.1 |
I ran into this today debugging a problem for a Panorama Partner. They couldn't get their Skyline instance to accept a valid Panorama server URL. They were getting a dialog with a message along the lines of "The server X is not a Panorama server"
The issue turned out to be that Tomcat had LabKey deployed to the root context path, meaning that the URLs didn't start with "/labkey"
There are at least a couple of places in PanoramaUtils.cs that assume /labkey-based URL, including:
/labkey/security/home/ensureLogin.view
/labkey/project/home/getContainers.view
I propose that we switch Skyline so that if you don't specify a context path when configuring a Panorama server URL, we try both the root and /labkey before giving up. We should also accept URLs that use other context paths for newly configured servers.