Sometimes you may need to blacklist a specific extension from being auto-installed, for example:
- the extension may not be compatible with the release of AIP Core you are using on your Node
- the extension may be known to cause specific issues for your environment
- the extension does not match your extension strategy (see Administration Center - Extensions Strategy / Administration Center - Settings - Extensions Strategy) - i.e. it is an alpha or beta and these are forbidden - and is requested automatically by Console
- the extension is not present in your Extend local server and is requested automatically by Console
Things to be aware of before blacklisting an extension:
- you cannot blacklist a specific release of an extension, it is all releases of the extension or not at all
- the blacklist configuration is performed at Node level, not global level (i.e. all Applications), therefore if you want to blacklist an extension for all Applications managed in Console, you will need to perform this action on all Nodes, or if you are using ≥ 2.8, you can use the blacklist option in Administration Center - Extensions Strategy.
Step 1 - Edit the configuration file
Edit the following file in a text editor:
Locate or add the following lines in to the file:
Add the IDs of the extensions you want to blacklist, separated by ";", for example (note that for ≥ 2.x, you must ensure that a space exists between blacklist: and the first extension ID):
Save the file when you have completed the changes.
Step 2 - Apply configuration changes
Restart the Node Windows Service (or batch file) to ensure all changes are taken into account.