Skip to main content
T
tmiller-31-Visitor
1-Visitor
June 20, 2016
Question

Integrity Licensing - Force timeout only for floating licenses

  • June 20, 2016
  • 2 replies
  • 2220 views

We have named/seat licenses as well as floating licenses for the Integrity client. In an effort to automatically force floating licenses to be freed, we have set mksis.im.httpSessionHeartbeat to false and mksis.im.httpSessionTimeout to 1800 seconds. The issue with these settings is that the named licenses are also being freed as licensees are kicked off at the 1800 second time.

How can we configure the licensing parameters so that ONLY floating licenses are experiencing the timeout? Otherwise, in order for someone else to login, we have to manually free a floating license. Imagine a group with 100 users and only 4 floating licenses. People login and then logoff but do not close their browser window, which would free the license that they just used.

    2 replies

    S
    ssaul15-Moonstone
    15-Moonstone
    June 23, 2016

    This is a feature request that we have open since 2004...

    It's RFC115337.

    PTC support told us that it is hard to implement, but eventually this simply does not fit into their business model...

    Feel free to contact support to be connected to this RFC and/or add an idea for this (we would vote for it)

      S
      sdavenport12-Amethyst
      12-Amethyst
      July 11, 2016

      Hi Ty,

      You’re right that this relates to RFC 115337 - today we don’t have the capability to omit seat license users from being disconnected every 60 minutes of in-activity. Since the posting of that RFC, we have changed our process so that product enhancements are now posted and voted on by customers directly as Product Ideas . We’ve yet to implement this functionality - if you can post an Idea for it, I would encourage sharing it on your community thread and getting others to vote for it. If you do, I can also update this KB article to point to your Idea so it gets more traffic if you like.

        Terms & ConditionsCookie settingsAccessibility statement