TestComplete Jenkins Integration- Login screen disable

[ShwethaShiva]

Hi,

Is it mandatory to disable the login screen and welcome message to run TestComplete scripts through Jenkins Pipeline? Is it not a security threat to our network by disabling the login screen?  Is anyone integrated Jenkins and Testcomplete in your organization? How did you resolve this issue without compromising security? Please help us to resolve this issue.

Thanks,

Shwetha

[Marsha_R]

Which login screen are you referring to?  

[ShwethaShiva]

Test Server  or Virtual machine user login screen

[Marsha_R]

Did you follow all these instructions in your setup?

https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/pipeline.html

[ShwethaShiva]

Yes, we followed all these steps.

TestComplete script successfully executed at the first time. The challenge we are facing is, When we run the test a second time “Unable to create a user session” error occurs. It requires the user to login to the server and disconnect  manually to execute  the script for the next time. It is only able to execute the test if we see the userID as disconnected status. 

[Marsha_R]

This archived thread has a discussion that sounds similar to what you are doing.  See if this helps.

https://community.smartbear.com/t5/TestComplete-General-Discussions/Unable-to-create-a-user-session-...

[ShwethaShiva]

Thanks for providing similar post. We referred requirements that need to be met document.

https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/requirements-and-li...

But our IT security team is not agreeing to disable Secure SIgn-In and legal notice message options, as it is a security threat for our network. Is there any other way we can solve this issue? Is it not a security threat to disable Secure Sign-In? 

[Marsha_R]

How do you sign in the first time the test is run and it's successful?

[ShwethaShiva]

Manually login and disconnected from the server. 

[Marsha_R]

It sounds like what you need to do is log out after every test run and log back in again rather than trying to do it all with one login.