Skip to main content
1-Visitor
October 18, 2014
Solved

How do we make our own Web Links that work like the Integrity Web Links?

  • October 18, 2014
  • 1 reply
  • 1855 views

Hi.

We have code for creating web links that works "kind of". See the code snippet below. When a user is using the Web Client, and they click on a link created by the interntals of Integrity, the user sees a page that allows them to view the item and switch to "edit item" from the left hand menu.

When a user clicks on an link created from the function below, the browser forces the user to login again. Our users want all links to function the same - whether those links are created by the internals of Integrity, or created by our custom scripts. So, how do we get the "Session Information", or whatever is needed, to make the links that we create in our scripts to function like the links created by Integrity?

Please advise.

-Sean

function GetWebLinkForItem(anID)

{

var weblink = new java.lang.StringBuffer();

weblink.append("http://");

weblink.append(eb.getHostname());

weblink.append(":7001/im/issues?selection=" );

weblink.append( anID.toString());

return weblink + "";

}

    Best answer by JoeBartlett

    The problem in this case ended-up being that the custom link was using the .getHostname() method from the siEnvironmentBean which got the fully qualified Integrity Server hostname (machine123.company.com). However, the users had an existing connection to Integrity using a DNS alias (server.company.com). Integrity sees these URLs as different connections since the hostnames are different and this is why users got the additional prompt.

    Article 187801 has been written to document these details.

    1 reply

    16-Pearl
    October 20, 2014

    Hi Sean,

    I don't have an answer for you for this, and I'm not even sure where to start trying to pull this kind of information from. Your best bet to get a prompt answer from PTC is to open a PTC Integrity Support case.

    Regards,

    Kael

    1-Visitor
    October 20, 2014

    Hi Kael,

    Thanks for the quick reply. I'll open a case for this one.

    -Sean

    21-Topaz I
    October 29, 2014

    The problem in this case ended-up being that the custom link was using the .getHostname() method from the siEnvironmentBean which got the fully qualified Integrity Server hostname (machine123.company.com). However, the users had an existing connection to Integrity using a DNS alias (server.company.com). Integrity sees these URLs as different connections since the hostnames are different and this is why users got the additional prompt.

    Article 187801 has been written to document these details.