Forum Discussion

ChiefBrian's avatar
ChiefBrian
Contributor
21 days ago

TestComplete\TestExecute constantly being logged out

Since the more recent updates we have been having constant issues with the programs being logged out and not being able to launch.

According to support part of the problem seems to be on Smartbears end since apparently when you login they create an access token on each local machine that is only good for 30 days.  Then they never update or refresh the token even if you launch the program every day for each of those 30 days.  So you get logged out and are forced to login every 30 days with no recourse or way to refresh that token.

They actually claim this is on purpose which is insane. Our customers would roast over the coals if we kicked them out of their software like this, especially when trying to run a critical procedure.

Their suggestion to generate an access token code on their website then pass that as a cmd line argument when launching the software.  They claim this won't have the same problems which I have not confirmed yet.  https://support.smartbear.com/testexecute/docs/licensing/id-based/automated-builds.html

It makes no sense that I have to generate a key, copy it and add it as an argument when I am already logged in. I also have this issue just launching the TC IDE which I am not launching from cmd line.  Why can they not just refresh the token each time I launch the software, it should be verifying my license validity each time any way, just update the last ping time date.

Anybody else having these constant problems?  This is somewhat new, we have been using the software for a decade plus, and this has not been a problem until recently(last 6 months or so).

Thanks.

4 Replies

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Icon for Champion Level 3 rankChampion Level 3
    21 days ago

    SmartBear’s documentation differentiates authentication based on interactive vs. automated usage when using ID-based licensing.

    For automated or unattended execution, the documentation states to use access tokens

    For interactive usage, such as the TestComplete IDE, the documented approach is to sign in using a SmartBear ID directly within the application UI.

    If there are concerns around session behavior or re-authentication expectations, those may be appropriate to raise through the TestComplete feature request forum:

    🤖 AI-assisted response
    👍 Found it helpful? Click Like
    ✅ Issue resolved? Click Mark as Solution

     

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    20 days ago

    I've never had TestComplete/Execute opened for more than 2 days, so I've never come across this issue before.

    I guess the 30 day token is meant to reduce how often you need to re-authenticate while still keeping things reasonably secure. It's security vs convenience trade-off!

  • MCH's avatar
    MCH
    Contributor
    13 days ago

    We have 14 Machines with TC and 5 with TE. All are logged in interactively. 
    The behaviour seems to differ a lot from machine to machine (or account to account). 
    We have machines where the login needs to be renewed every 30 days but some machines seem to be logged out much earlier. 
    This leads to not being able to start our nightly test runs started by our management tool via dll on those machines and means we have no results for a number of tests on the next day. 
    It get's really annoying if this happens couple times a week. Once every month would also not be perfect but bearable. 

  • ChiefBrian's avatar
    ChiefBrian
    Contributor
    13 days ago

    I agree the behavior seems to be somewhat random, and more often than every 30 days on some machines.  The 30 day number came from support and I have not yet tried to track if that is actually what I am seeing.

    I had zoom meeting with support this week and they again confirmed the only way to run automated tests without being logged out was to use the access key method.  So far, since implementing this I have not seen my tests fail for this reason.  I do however still get asked to login when I try to manually launch TC or TE, which is less problematic but still annoying.

    I've never had TestComplete/Execute opened for more than 2 days, so I've never come across this issue before.

    I guess the 30 day token is meant to reduce how often you need to re-authenticate while still keeping things reasonably secure. It's security vs convenience trade-off!

    This makes no sense.