Hello All!
I’m using the “Analyze File” function, but I’m encountering the following error:
![]()
How can I handle this error? I’m obtaining the credentials from the orchestrator and using them to log onto the SQL Server.
Hello All!
I’m using the “Analyze File” function, but I’m encountering the following error:
![]()
How can I handle this error? I’m obtaining the credentials from the orchestrator and using them to log onto the SQL Server.
This is not a blocker for your execution, if it is blocking to execute or publish you can modify it
to modify follow below steps,
1.open Workflow Analyzer settings
2. Search with ST-SEC-008
3. you can get the results there you can see the Default type as error change to warn or any other option.
4. click on Ok and proceed with your automation.
Happy Automation!!
Keep your credential variable and use them closely. Like this. Variable scope should be inside that single sequence.
Hey @Erick_Richeter ok so you creating the securestring variable to log into some portal or any application you are accessing. these error rectifying that the Variable you created in for example sequence1 and now you are using it to sequence2. so use that variable inside that sequence.
cheers
Hi @Erick_Richeter,
This error happens when you are fetching secure creds outside of the immediate scope.
Per secure string related workflow analyzer rules,
Hope this helps.
Regards
Sonali
Thank you, @singh_sumit and @ashokkarale. I adjusted the scope of my application to keep my secure string within the same scope. I also appreciate the explanation, @sonaliaggarwal47 !
Its a rule that the REFramework violates (at least in the one that is modified to load credentials to the Config Dictionary), but it doesnt proc the rule because the securestring is in a Dictionary<string, SecureString> and it doesnt realize the SecureString in the Dictionary.
It in my opinion should only be a warning as its not so serious if you pass from one workflow to another as thats no different than passing it from the workflow to the activity that uses it.
That being said, it is a good idea to keep the scope small, however I’ve suggest not only doing that with Credential type assets but all assets, ditch the config and just grab an asset the moment you need it.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.