Installation Location

Adapters are defined to be in a namespace. This is important to understand as the adapter should be in that namespace within the IAP node_modules directory. If it is installed in a directory that does not match the namespace defined in the adapter files (e.g. package.json, pronghorn.json, etc) the adapter will not come up.

IAP used to accept uppercase letters in namespaces, but in newer releases what the namespace can contain has been changed to be in line with npm rules - which means uppercase letters are no longer valid. While the adapter will still load if the namespace has uppercase letters, you will not be able to set IAP Service Instance Configuration values within IAP Admin Essentials unless you modify the namespace of the adapter.

Most Itential adapters exist in the @itentialopensource namespace. This means they should be installed in the IAP-Home/node_modules/@itentialopensource directory. For example:
/opt/itential/current/node_modules/@itentialopensource/adapter-aws_ec2

There are Itential adapters that come with IAP by default which are in the @itential namespace. These adapters include several IAP authentication adapters (e.g., adapter-ldap) as well as some of the more specialized orchestration adapters (e.g., adapter-nso). These would typically be in the IAP-Home/node_modules/@itential directory. For example: /opt/itential/current/node_modules/@itential/adapter-nso

There are also custom adapters that Itential Professional Services or our customers build that may have their own namespace (e.g., @mycompany). These adapters would be installed in their own namespace directory IAP-Home/node_modules/@mycompany. For example:
/opt/itential/current/node_modules/@mycompany/adapter-mycustomadapter

Note: If the adapter is not installed in the proper directory, the adapter will fail to load when IAP is restarted.