So Dynamics/D365 requires setting up of an app in Azure Portal along with a certificate / secret.
and by using the KingswaySoft tool for SSIS, I can successfully extract and import data into the data warehouse.
Now the certificate / secret has expired, and have been told a new one will be required with a new secret value.
This is a problem in that I have 30 SSIS packages with the current secret value and the only way I can update it is manually updating each package - which is time-consuming as I've created the connection per package (not project - had issues with this).
Any ideas on how to handle this situation?
I would prefer the existing certificate / secret to continue to work (reactive). Or do a find and replace on each dtsx using notepad but the value is encrypted - so can't do that.
Assuming you have deployed to SSISDB ...
Use an environment in SSISDB and create a sensitive parameter to contain the secret value.
Configure your SSISDB project to reference the environment and then override the default value of the parameter (as defined in the package) with the value from the environment.
Once you have this in place, changing the secret value in future is as simple as updating that one SSISDB parameter.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
February 21, 2024 at 10:47 am
Thank you Phil, I think that will work when I do deploy to the SSISDB.
At the moment, dataverse is constantly being update with a new/deleted/updated columns which is why I manually run the packages (as and when needed), plus its in dev environment only.
So I'll probably manually update each package for now and then use once deployed look at creating a sensitive parameter within SSISDB.
February 21, 2024 at 11:17 am
Thank you Phil, I think that will work when I do deploy to the SSISDB.
At the moment, dataverse is constantly being update with a new/deleted/updated columns which is why I manually run the packages (as and when needed), plus its in dev environment only.
So I'll probably manually update each package for now and then use once deployed look at creating a sensitive parameter within SSISDB.
Fair enough.
A shared project-level connection sounds like it should work in this case, though you will have to be careful with protection levels. If you would like help resolving the 'issues' you had with that, please feel free to post again.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply