SecurityCredentials binding

Replies to This Discussion

Permalink Reply by Joe Klug on January 3, 2017 at 8:45am

Is this for a client connector or service connector?  For service connectors you can assign environment variables to each component of the credential:

Windows Domain

User Name

Password

You can assign these through the Binding button.

• ▶ Reply

Permalink Reply by FabrizioM. on January 4, 2017 at 6:04am

Hi Joe,
it's the client endpoint, in particular the Access Control List.
The problem is that when I configure the Credential as windows domain, I can only get access to the domain where my development machine is located, not the DMZ domain.

Do you have any workaround in mind?

• ▶ Reply

Permalink Reply by Joe Klug on January 4, 2017 at 9:16am

Ok, got it. Unfortunately we need Neuron ESB explorer to be connected to the Windows Domain you're saving credentials for because we save the SID of the Windows user for comparison with the incoming credentials. Here's one suggestion, and it's a one-time effort. Copy your solution to either the production server or a temp machine that is on the DMZ domain. Open the solution in Neuron ESB Explorer and add the credentials you need and create an ACL for that domain. Then move that solution back to your dev environment. You'll need to create an environment variable for which ACL to use, and then set the binding property "ACL" to the environment variable name. I know, not ideal. But we need to capture that SID. The good news is that if the passwords change, you don't need to redo the steps above. You can just change the DMZ domain account passwords in the dev environment - the original SID should be retained.

• ▶ Reply

Permalink Reply by FabrizioM. on January 6, 2017 at 5:44am

Hi Joe,
thank you very much for the suggestions, I'll test it and let you know.

Fabrizio

• ▶ Reply