0
Planned

Private workflow unit test case error - unauthorized to execute

jigar.patel 2 weeks ago in Studio updated by Siphamandla Dube 1 week ago 2

I have created one workflow that workflow can not be accessed via public URl. I have created test case for that workflow and selected Run As Public workflow. Now I am facing error like unauthorized to execute.


Meeting video link for reference.

https://theunlimited-my.sharepoint.com/:v:/g/personal/khushbu_desai_theunlimited_co_za/EaooH-nvZSJAval0VGcbDFIBqmJF8q_b33MfFP-WX2J2RA

Answer

Answer
Planned

Hello Jigar,

Thank you for bringing this issue to our attention.

The User selection should indeed be sending the Server_Name and Server_Password of the Server the tests sit-in, which is currently not the case with our codebase, the Public select should also be sending its payload as an anonymous user so this behavior can be tested correctly and hence this ticket will be used to enhance this framework in regards to these behaviors.

However, the security of the Warewolf server will not be in your way should you provide the server the tests sits-in with the Server_Name and Server_Password included in the URL as follows: 
http://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet" title="http://%5b%5bserver_name%5d%5d:%5b%5bserver_pasword%5d%5d@localhost:54914/secure/hello%20world.tests?name=etetet" href="http://%5B%5BSERVER_NAME%5D%5D:%5B%5BSERVER_PASWORD%5D%5D@localhost:54914/secure/Hello%20World.tests?Name=etetet" rel="noopener noreferrer" target="_blank" tabindex="-1">HTTP://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet


Hope this suggestion helps you resolve the critical part of your issue.

Kind regards

Siphamandla Dube

Answer
Planned

Hello Jigar,

Thank you for bringing this issue to our attention.

The User selection should indeed be sending the Server_Name and Server_Password of the Server the tests sit-in, which is currently not the case with our codebase, the Public select should also be sending its payload as an anonymous user so this behavior can be tested correctly and hence this ticket will be used to enhance this framework in regards to these behaviors.

However, the security of the Warewolf server will not be in your way should you provide the server the tests sits-in with the Server_Name and Server_Password included in the URL as follows: 
http://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet" title="http://%5b%5bserver_name%5d%5d:%5b%5bserver_pasword%5d%5d@localhost:54914/secure/hello%20world.tests?name=etetet" href="http://%5B%5BSERVER_NAME%5D%5D:%5B%5BSERVER_PASWORD%5D%5D@localhost:54914/secure/Hello%20World.tests?Name=etetet" rel="noopener noreferrer" target="_blank" tabindex="-1">HTTP://[[SERVER_NAME]]:[[SERVER_PASWORD]]@localhost:54914/secure/Hello%20World.tests?Name=etetet


Hope this suggestion helps you resolve the critical part of your issue.

Kind regards

Siphamandla Dube