Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Inject credentials into bindings from SSO #414

Open
tfabraham opened this issue Nov 6, 2017 · 5 comments
Open

[Feature] Inject credentials into bindings from SSO #414

tfabraham opened this issue Nov 6, 2017 · 5 comments

Comments

@tfabraham
Copy link
Member

tfabraham commented Nov 6, 2017

This would be useful for injecting passwords into bindings files where adapters don't support SSO (see: http://stackoverflow.com/a/37174322/1750471). This way we don't need to store passwords in source control.

What we would like is:

BTDF injects passwords into bindings files getting these credentials from SSO.
Bindings file with credentials is saved temporary location (which users would need to secure) and destroy this file immediately after use (even if errors occurs mid deployment).

This work item was migrated from CodePlex

CodePlex work item ID: '11089'
Vote count: '3'

@fernandodsanjos
Copy link

Hi
Is it possible via some script to update the binding, some event in where we can get and update the bindingfile before it is imported?

@eloekset
Copy link

Support various sources, like Azure KeyVault.

@fernandodsanjos
Copy link

We now have an app that injects/replaces password placeholders in the settingsfile using KeyVault. The placeholders must be named the same as an existing secret.

@akishaha
Copy link

We now have an app that injects/replaces password placeholders in the settingsfile using KeyVault. The placeholders must be named the same as an existing secret.

How did you achieved it ?

@fernandodsanjos
Copy link

fernandodsanjos commented Dec 6, 2021

We now have an app that injects/replaces password placeholders in the settingsfile using KeyVault. The placeholders must be named the same as an existing secret.

How did you achieved it ?

Using a custom target
<Target Name="InjectAzureCredentials" AfterTargets="PreprocessBindings" Condition="'$(Configuration)' != 'Server'"> <Exec Command="ICC.Shared.Utilities.InjectAzureCredentials.exe"/> </Target>

The executable searches all tags that looks like $[tagname] with the value from azure secret with the same name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants