Credentials issue for Microsoft AD spoke

[Jithendra Kumar]

Hi All,

We have recently installed IntegrationHub and setting up the things to use Microsoft AD spoke.

I have created the Credentials record by giving the Username and Password of the Service account. While trying to test the credentials by clicking on "Test Credential" related link, i'm getting Authentication Failed error and i could see below error in the ECC queue:

<results error="Adding target to blacklist.  No valid credential found for type [Windows]" probe_time="1032" result_code="42"><result error="Adding target to blacklist.  No valid credential found for type [Windows]"

Any pointers on how to resolve this issue would be really helpful.

Please note that Service Account credentials are correct as i was able to login to MID server host using the same credentials.

~Jit.

[alexgg57]

What Action(s) do you use by this? Any OOB, or how you got the error by?

If you use the custom action, then make sure your powershell inputs has credType=AD.

OOB should have it by default.

Let me know your scenario.

Thanks.

[Jithendra Kumar]

I'm getting this error when trying to test the credential record that I've created by clicking on "Test credential" related link. Since I was blocked at this very initial stage, I haven't used any actions yet. Thanks!!

[alexgg57]

The connection test has some tends do not show truth 😞

I would recommend you just test with real action, e.g. "lookup user", then if you get an error, please provide it here.

[Jithendra Kumar]

Hi All,

I have managed to get through this error by providing local admin privileges to the Service Account on the target host.

As a next step i have created a Sample catalog item and a sample flow by using AD Spoke action "Add User To Group". Upon submission of the catalog item the flow is getting triggered without any issue but the AD Spoke action is throwing below runtime error. Any pointers on this would be really helpful.

The term 'SNCLog-ParameterInfo' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Stack Trace:    at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)