Adapter
Adapter for Integration to BlueCat
Overview
This adapter is used to integrate the Itential Automation Platform (IAP) with the Bluecat System. The API that was used to build the adapter for Bluecat is usually available in the report directory of this adapter. The adapter utilizes the Bluecat API to provide the integrations that are deemed pertinent to IAP. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
Details
The BlueCat adapter from Itential is used to integrate the Itential Automation Platform (IAP) with BlueCat. With this adapter you have the ability to perform operations such as:
- Performs IP management, DNS management, and data center management.
For further technical details on how to install and use this adapter, please click the Technical Documentation tab.
BlueCat
Table of Contents
Getting Started
These instructions will help you get a copy of the project on your local machine for development and testing. Reading this section is also helpful for deployments as it provides you with pertinent information on prerequisites and properties.
Helpful Background Information
There is Adapter documentation available on the Itential Documentation Site. This documentation includes information and examples that are helpful for:
Authentication
IAP Service Instance Configuration
Code Files
Endpoint Configuration (Action & Schema)
Mock Data
Adapter Generic Methods
Headers
Security
Linting and Testing
Build an Adapter
Troubleshooting an Adapter
Others will be added over time. Want to build a new adapter? Use the Itential Adapter Builder
Prerequisites
The following is a list of required packages for installation on the system the adapter will run on:
Node.js
npm
Git
The following list of packages are required for Itential opensource adapters or custom adapters that have been built utilizing the Itential Adapter Builder. You can install these packages by running npm install inside the adapter directory.
Package | Description |
---|---|
@itentialopensource/adapter-utils | Runtime library classes for all adapters; includes request handling, connection, authentication throttling, and translation. |
ajv | Required for validation of adapter properties to integrate with Bluecat. |
axios | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
commander | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
dns-lookup-promise | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
fs-extra | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
mocha | Testing library that is utilized by some of the node scripts that are included with the adapter. |
mocha-param | Testing library that is utilized by some of the node scripts that are included with the adapter. |
mongodb | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
nyc | Testing coverage library that is utilized by some of the node scripts that are included with the adapter. |
ping | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
readline-sync | Utilized by the node script that comes with the adapter; helps to test unit and integration functionality. |
semver | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
winston | Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality. |
If you are developing and testing a custom adapter, or have testing capabilities on an Itential opensource adapter, you will need to install these packages as well.
chai
eslint
eslint-config-airbnb-base
eslint-plugin-import
eslint-plugin-json
testdouble
How to Install
- Set up the name space location in your IAP node_modules.
cd /opt/pronghorn/current/node_modules (* could be in a different place)
if the @itentialopensource directory does not exist, create it:
mkdir @itentialopensource
- Clone/unzip/tar the adapter into your IAP environment.
cd \@itentialopensource
git clone git@gitlab.com:\@itentialopensource/adapters/adapter-bluecat
or
unzip adapter-bluecat.zip
or
tar -xvf adapter-bluecat.tar
- Run the adapter install script.
cd adapter-bluecat
npm install
npm run lint:errors
npm run test
- Restart IAP
systemctl restart pronghorn
Create an adapter service instance configuration in IAP Admin Essentials GUI
Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
- Install adapter dependencies and check the adapter.
cd adapter-bluecat
npm run adapter:install
- Restart IAP
systemctl restart pronghorn
- Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
Testing
Mocha is generally used to test all Itential Opensource Adapters. There are unit tests as well as integration tests performed. Integration tests can generally be run as standalone using mock data and running the adapter in stub mode, or as integrated. When running integrated, every effort is made to prevent environmental failures, however there is still a possibility.
Unit Testing
Unit Testing includes testing basic adapter functionality as well as error conditions that are triggered in the adapter prior to any integration. There are two ways to run unit tests. The prefered method is to use the testRunner script; however, both methods are provided here.
node utils/testRunner --unit
npm run test:unit
npm run test:baseunit
To add new unit tests, edit the test/unit/adapterTestUnit.js
file. The tests that are already in this file should provide guidance for adding additional tests.
Integration Testing - Standalone
Standalone Integration Testing requires mock data to be provided with the entities. If this data is not provided, standalone integration testing will fail. When the adapter is set to run in stub mode (setting the stub property to true), the adapter will run through its code up to the point of making the request. It will then retrieve the mock data and return that as if it had received that data as the response from Bluecat. It will then translate the data so that the adapter can return the expected response to the rest of the Itential software. Standalone is the default integration test.
Similar to unit testing, there are two ways to run integration tests. Using the testRunner script is better because it prevents you from having to edit the test script; it will also resets information after testing is complete so that credentials are not saved in the file.
node utils/testRunner
answer no at the first prompt
npm run test:integration
To add new integration tests, edit the test/integration/adapterTestIntegration.js
file. The tests that are already in this file should provide guidance for adding additional tests.
Integration Testing
Integration Testing requires connectivity to Bluecat. By using the testRunner script it prevents you from having to edit the integration test. It also resets the integration test after the test is complete so that credentials are not saved in the file.
Note: These tests have been written as a best effort to make them work in most environments. However, the Adapter Builder often does not have the necessary information that is required to set up valid integration tests. For example, the order of the requests can be very important and data is often required for
creates
andupdates
. Hence, integration tests may have to be enhanced before they will work (integrate) with Bluecat. Even after tests have been set up properly, it is possible there are environmental constraints that could result in test failures. Some examples of possible environmental issues are customizations that have been made within Bluecat which change order dependencies or required data.
node utils/testRunner
answer yes at the first prompt
answer all other questions on connectivity and credentials
Test should also be written to clean up after themselves. However, it is important to understand that in some cases this may not be possible. In addition, whenever exceptions occur, test execution may be stopped, which will prevent cleanup actions from running. It is recommended that tests be utilized in dev and test labs only.
Reminder: Do not check in code with actual credentials to systems.
Configuration
This section defines all the properties that are available for the adapter, including detailed information on what each property is for. If you are not using certain capabilities with this adapter, you do not need to define all of the properties. An example of how the properties for this adapter can be used with tests or IAP are provided in the sampleProperties.
Example Properties
"properties": {
"host": "localhost",
"port": 443,
"choosepath": "",
"base_path": "/",
"version": "",
"cache_location": "none",
"encode_pathvars": true,
"encode_queryvars": true,
"save_metric": false,
"stub": true,
"protocol": "https",
"authentication": {
"auth_method": "request_token",
"username": "username",
"password": "password",
"token": "token",
"token_timeout": 1800000,
"token_cache": "local",
"invalid_token_error": 401,
"auth_field": "header.headers.Authorization",
"auth_field_format": "{token}",
"auth_logging": false,
"client_id": "",
"client_secret": "",
"grant_type": "",
"sensitive": [],
"sso": {
"protocol": "",
"host": "",
"port": 0
},
"multiStepAuthCalls": [
{
"name": "",
"requestFields": {},
"responseFields": {},
"successfullResponseCode": 200
}
]
},
"healthcheck": {
"type": "none",
"frequency": 60000,
"query_object": {},
"addlHeaders": {}
},
"throttle": {
"throttle_enabled": false,
"number_pronghorns": 1,
"sync_async": "sync",
"max_in_queue": 1000,
"concurrent_max": 1,
"expire_timeout": 0,
"avg_runtime": 200,
"priorities": [
{
"value": 0,
"percent": 100
}
]
},
"request": {
"number_redirects": 0,
"number_retries": 3,
"limit_retry_error": [
0
],
"failover_codes": [],
"attempt_timeout": 5000,
"global_request": {
"payload": {},
"uriOptions": {},
"addlHeaders": {},
"authData": {}
},
"healthcheck_on_timeout": true,
"return_raw": false,
"archiving": false,
"return_request": false
},
"proxy": {
"enabled": false,
"host": "",
"port": 1,
"protocol": "http",
"username": "",
"password": ""
},
"ssl": {
"ecdhCurve": "",
"enabled": false,
"accept_invalid_cert": false,
"ca_file": "",
"key_file": "",
"cert_file": "",
"secure_protocol": "",
"ciphers": ""
},
"mongo": {
"host": "",
"port": 0,
"database": "",
"username": "",
"password": "",
"replSet": "",
"db_ssl": {
"enabled": false,
"accept_invalid_cert": false,
"ca_file": "",
"key_file": "",
"cert_file": ""
}
},
"devicebroker": {
"getDevice": [
{
"path": "/get/devices/{id}",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"id": "name"
},
"responseDatakey": "",
"responseFields": {
"name": "host",
"ostype": "os",
"ostypePrefix": "system-",
"ipaddress": "attributes.ipaddr",
"port": "443"
}
}
],
"getDevicesFiltered": [
{
"path": "/get/devices",
"method": "GET",
"pagination": {
"offsetVar": "",
"limitVar": "",
"incrementBy": "limit",
"requestLocation": "query"
},
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {
"name": "host",
"ostype": "os",
"ostypePrefix": "system-",
"ipaddress": "attributes.ipaddr",
"port": "443"
}
}
],
"isAlive": [
{
"path": "/get/devices/{id}/status",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"id": "name"
},
"responseDatakey": "",
"responseFields": {
"status": "status",
"statusValue": "online"
}
}
],
"getConfig": [
{
"path": "/get/devices/{id}/configPart1",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"id": "name"
},
"responseDatakey": "",
"responseFields": {}
}
],
"getCount": [
{
"path": "/get/devices",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {}
}
]
},
"cache": {
"enabled": false,
"entities": [
{
"entityType": "",
"frequency": 1440,
"flushOnFail": false,
"limit": 1000,
"retryAttempts": 5,
"sort": true,
"populate": [
{
"path": "",
"method": "GET",
"pagination": {
"offsetVar": "",
"limitVar": "",
"incrementBy": "limit",
"requestLocation": "query"
},
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {}
}
],
"cachedTasks": [
{
"name": "",
"filterField": "",
"filterLoc": ""
}
]
}
]
}
}
Connection Properties
These base properties are used to connect to Bluecat upon the adapter initially coming up. It is important to set these properties appropriately.
Property | Description |
---|---|
host | Required. A fully qualified domain name or IP address. |
port | Required. Used to connect to the server. |
base_path | Optional. Used to define part of a path that is consistent for all or most endpoints. It makes the URIs easier to use and maintain but can be overridden on individual calls. An example **base_path** might be `/rest/api`. Default is ``. |
version | Optional. Used to set a global version for action endpoints. This makes it faster to update the adapter when endpoints change. As with the base-path, version can be overridden on individual endpoints. Default is ``. |
cache_location | Optional. Used to define where the adapter cache is located. The cache is used to maintain an entity list to improve performance. Storage locally is lost when the adapter is restarted. Storage in Redis is preserved upon adapter restart. Default is none which means no caching of the entity list. |
encode_pathvars | Optional. Used to tell the adapter to encode path variables or not. The default behavior is to encode them so this property can be used to stop that behavior. |
encode_queryvars | Optional. Used to tell the adapter to encode query parameters or not. The default behavior is to encode them so this property can be used to stop that behavior. |
save_metric | Optional. Used to tell the adapter to save metric information (this does not impact metrics returned on calls). This allows the adapter to gather metrics over time. Metric data can be stored in a database or on the file system. |
stub | Optional. Indicates whether the stub should run instead of making calls to Bluecat (very useful during basic testing). Default is false (which means connect to Bluecat). |
protocol | Optional. Notifies the adapter whether to use HTTP or HTTPS. Default is HTTP. |
A connectivity check tells IAP the adapter has loaded successfully.
Authentication Properties
The following properties are used to define the authentication process to Bluecat.
Note: Depending on the method that is used to authenticate with Bluecat, you may not need to set all of the authentication properties.
Property | Description |
---|---|
auth_method | Required. Used to define the type of authentication currently supported. Authentication methods currently supported are: `basic user_password`, `static_token`, `request_token`, and `no_authentication`. |
username | Used to authenticate with Bluecat on every request or when pulling a token that will be used in subsequent requests. |
password | Used to authenticate with Bluecat on every request or when pulling a token that will be used in subsequent requests. |
token | Defines a static token that can be used on all requests. Only used with `static_token` as an authentication method (auth\_method). |
invalid_token_error | Defines the HTTP error that is received when the token is invalid. Notifies the adapter to pull a new token and retry the request. Default is 401. |
token_timeout | Defines how long a token is valid. Measured in milliseconds. Once a dynamic token is no longer valid, the adapter has to pull a new token. If the token_timeout is set to -1, the adapter will pull a token on every request to Bluecat. If the timeout_token is 0, the adapter will use the expiration from the token response to determine when the token is no longer valid. |
token_cache | Used to determine where the token should be stored (local memory or in Redis). |
auth_field | Defines the request field the authentication (e.g., token are basic auth credentials) needs to be placed in order for the calls to work. |
auth_field_format | Defines the format of the auth\_field. See examples below. Items enclosed in {} inform the adapter to perofrm an action prior to sending the data. It may be to replace the item with a value or it may be to encode the item. |
auth_logging | Setting this true will add some additional logs but this should only be done when trying to debug an issue as certain credential information may be logged out when this is true. |
client_id | Provide a client id when needed, this is common on some types of OAuth. |
client_secret | Provide a client secret when needed, this is common on some types of OAuth. |
grant_type | Provide a grant type when needed, this is common on some types of OAuth. |
Examples of authentication field format
"{token}"
"Token {token}"
"{username}:{password}"
"Basic {b64}{username}:{password}{/b64}"
Healthcheck Properties
The healthcheck properties defines the API that runs the healthcheck to tell the adapter that it can reach Bluecat. There are currently three types of healthchecks.
- None - Not recommended. Adapter will not run a healthcheck. Consequently, unable to determine before making a request if the adapter can reach Bluecat.
- Startup - Adapter will check for connectivity when the adapter initially comes up, but it will not check afterwards.
- Intermittent - Adapter will check connectivity to Bluecat at a frequency defined in the
frequency
property.
Property | Description |
---|---|
type | Required. The type of health check to run. |
frequency | Required if intermittent. Defines how often the health check should run. Measured in milliseconds. Default is 300000. |
query_object | Query parameters to be added to the adapter healthcheck call. |
Request Properties
The request section defines properties to help handle requests.
Property | Description |
---|---|
number_redirects | Optional. Tells the adapter that the request may be redirected and gives it a maximum number of redirects to allow before returning an error. Default is 0 - no redirects. |
number_retries | Tells the adapter how many times to retry a request that has either aborted or reached a limit error before giving up and returning an error. |
limit_retry_error | Optional. Can be either an integer or an array. Indicates the http error status number to define that no capacity was available and, after waiting a short interval, the adapter can retry the request. If an array is provvided, the array can contain integers or strings. Strings in the array are used to define ranges (e.g. "502-506"). Default is [0]. |
failover_codes | An array of error codes for which the adapter will send back a failover flag to IAP so that the Platform can attempt the action in another adapter. |
attempt_timeout | Optional. Tells how long the adapter should wait before aborting the attempt. On abort, the adapter will do one of two things: 1) return the error; or 2) if **healthcheck\_on\_timeout** is set to true, it will abort the request and run a Healthcheck until it re-establishes connectivity to Bluecat, and then will re-attempt the request that aborted. Default is 5000 milliseconds. |
global_request | Optional. This is information that the adapter can include in all requests to the other system. This is easier to define and maintain than adding this information in either the code (adapter.js) or the action files. |
global_request -> payload | Optional. Defines any information that should be included on all requests sent to the other system that have a payload/body. |
global_request -> uriOptions | Optional. Defines any information that should be sent as untranslated query options (e.g. page, size) on all requests to the other system. |
global_request -> addlHeaders | Optioonal. Defines any headers that should be sent on all requests to the other system. |
global_request -> authData | Optional. Defines any additional authentication data used to authentice with the other system. This authData needs to be consistent on every request. |
healthcheck_on_timeout | Required. Defines if the adapter should run a health check on timeout. If set to true, the adapter will abort the request and run a health check until it re-establishes connectivity and then it will re-attempt the request. |
return_raw | Optional. Tells the adapter whether the raw response should be returned as well as the IAP response. This is helpful when running integration tests to save mock data. It does add overhead to the response object so it is not ideal from production. |
archiving | Optional flag. Default is false. It archives the request, the results and the various times (wait time, Bluecat time and overall time) in the `adapterid_results` collection in MongoDB. Although archiving might be desirable, be sure to develop a strategy before enabling this capability. Consider how much to archive and what strategy to use for cleaning up the collection in the database so that it does not become too large, especially if the responses are large. |
return_request | Optional flag. Default is false. Will return the actual request that is made including headers. This should only be used during debugging issues as there could be credentials in the actual request. |
SSL Properties
The SSL section defines the properties utilized for ssl authentication with Bluecat. SSL can work two different ways: set the accept\_invalid\_certs
flag to true (only recommended for lab environments), or provide a ca\_file
.
Property | Description |
---|---|
enabled | If SSL is required, set to true. |
accept_invalid_certs | Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false. |
ca_file | Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required. |
key_file | Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL. |
cert_file | Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL. |
secure_protocol | Defines the protocol (e.g., SSLv3_method) to use on the SSL request. |
ciphers | Required if SSL enabled. Specifies a list of SSL ciphers to use. |
ecdhCurve | During testing on some Node 8 environments, you need to set `ecdhCurve` to auto. If you do not, you will receive PROTO errors when attempting the calls. This is the only usage of this property and to our knowledge it only impacts Node 8 and 9. |
Throttle Properties
The throttle section is used when requests to Bluecat must be queued (throttled). All of the properties in this section are optional.
Property | Description |
---|---|
throttle_enabled | Default is false. Defines if the adapter should use throttling or not. |
number_pronghorns | Default is 1. Defines if throttling is done in a single Itential instance or whether requests are being throttled across multiple Itential instances (minimum = 1, maximum = 20). Throttling in a single Itential instance uses an in-memory queue so there is less overhead. Throttling across multiple Itential instances requires placing the request and queue information into a shared resource (e.g. database) so that each instance can determine what is running and what is next to run. Throttling across multiple instances requires additional I/O overhead. |
sync-async | This property is not used at the current time (it is for future expansion of the throttling engine). |
max_in_queue | Represents the maximum number of requests the adapter should allow into the queue before rejecting requests (minimum = 1, maximum = 5000). This is not a limit on what the adapter can handle but more about timely responses to requests. The default is currently 1000. |
concurrent_max | Defines the number of requests the adapter can send to Bluecat at one time (minimum = 1, maximum = 1000). The default is 1 meaning each request must be sent to Bluecat in a serial manner. |
expire_timeout | Default is 0. Defines a graceful timeout of the request session. After a request has completed, the adapter will wait additional time prior to sending the next request. Measured in milliseconds (minimum = 0, maximum = 60000). |
average_runtime | Represents the approximate average of how long it takes Bluecat to handle each request. Measured in milliseconds (minimum = 50, maximum = 60000). Default is 200. This metric has performance implications. If the runtime number is set too low, it puts extra burden on the CPU and memory as the requests will continually try to run. If the runtime number is set too high, requests may wait longer than they need to before running. The number does not need to be exact but your throttling strategy depends heavily on this number being within reason. If averages range from 50 to 250 milliseconds you might pick an average run-time somewhere in the middle so that when Bluecat performance is exceptional you might run a little slower than you might like, but when it is poor you still run efficiently. |
priorities | An array of priorities and how to handle them in relation to the throttle queue. Array of objects that include priority value and percent of queue to put the item ex { value: 1, percent: 10 } |
Proxy Properties
The proxy section defines the properties to utilize when Bluecat is behind a proxy server.
Property | Description |
---|---|
enabled | Required. Default is false. If Bluecat is behind a proxy server, set enabled flag to true. |
host | Host information for the proxy server. Required if `enabled` is true. |
port | Port information for the proxy server. Required if `enabled` is true. |
protocol | The protocol (i.e., http, https, etc.) used to connect to the proxy. Default is http. |
username | If there is authentication for the proxy, provide the username here. |
password | If there is authentication for the proxy, provide the password here. |
Mongo Properties
The mongo section defines the properties used to connect to a Mongo database. Mongo can be used for throttling as well as to persist metric data. If not provided, metrics will be stored in the file system.
Property | Description |
---|---|
host | Optional. Host information for the mongo server. |
port | Optional. Port information for the mongo server. |
database | Optional. The database for the adapter to use for its data. |
username | Optional. If credentials are required to access mongo, this is the user to login as. |
password | Optional. If credentials are required to access mongo, this is the password to login with. |
replSet | Optional. If the database is set up to use replica sets, define it here so it can be added to the database connection. |
db_ssl | Optional. Contains information for SSL connectivity to the database. |
db_ssl -> enabled | If SSL is required, set to true. |
db_ssl -> accept_invalid_cert | Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false. |
db_ssl -> ca_file | Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required. |
db_ssl -> key_file | Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL. |
db_ssl -> cert_file | Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL. |
Device Broker Properties
The device broker section defines the properties used integrate Bluecat to the device broker. Each broker call is represented and has an array of calls that can be used to build the response. This describes the calls and then the fields which are available in the calls.
Property | Description |
---|---|
getDevice | The array of calls used to get device details for the broker |
getDevicesFiltered | The array of calls used to get devices for the broker |
isAlive | The array of calls used to get device status for the broker |
getConfig | The array of calls used to get device configuration for the broker |
getCount | The array of calls used to get device configuration for the broker |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> path | The path, not including the base_path and version, for making this call |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> method | The rest method for making this call |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> query | Query object containing and query parameters and their values for this call |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> body | Body object containing the payload for this call |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> headers | Header object containing the headers for this call. |
getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> handleFailure | Tells the adapter whether to "fail" or "ignore" failures if they occur. |
isAlive -> statusValue | Tells the adapter what value to look for in the status field to determine if the device is alive. |
getDevice/getDevicesFiltered/isAlive/getConfig -> requestFields | Object containing fields the adapter should send on the request and where it should get the data. The where can be from a response to a getDevicesFiltered or a static value. |
getDevice/getDevicesFiltered/isAlive/getConfig -> responseFields | Object containing fields the adapter should set to send back to iap and where the value should come from in the response or request data. |
Using this Adapter
The adapter.js
file contains the calls the adapter makes available to the rest of the Itential Platform. The API detailed for these calls should be available through JSDOC. The following is a brief summary of the calls.
Generic Adapter Calls
These are adapter methods that IAP or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
Method Signature | Description | Workflow? |
---|---|---|
connect() | This call is run when the Adapter is first loaded by he Itential Platform. It validates the properties have been provided correctly. | No |
healthCheck(callback) | This call ensures that the adapter can communicate with Adapter for BlueCat. The actual call that is used is defined in the adapter properties and .system entities action.json file. | No |
refreshProperties(properties) | This call provides the adapter the ability to accept property changes without having to restart the adapter. | No |
encryptProperty(property, technique, callback) | This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Adapter for BlueCat. | No |
iapUpdateAdapterConfiguration(configFile, changes, entity, type, action, callback) | This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations. | Yes |
iapSuspendAdapter(mode, callback) | This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed. | Yes |
iapUnsuspendAdapter(callback) | This call provides the ability to resume a suspended adapter. Any requests in queue will be processed before new requests. | Yes |
iapGetAdapterQueue(callback) | This call will return the requests that are waiting in the queue if throttling is enabled. | Yes |
iapFindAdapterPath(apiPath, callback) | This call provides the ability to see if a particular API path is supported by the adapter. | Yes |
iapTroubleshootAdapter(props, persistFlag, adapter, callback) | This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls. | Yes |
iapRunAdapterHealthcheck(adapter, callback) | This call will return the results of a healthcheck. | Yes |
iapRunAdapterConnectivity(callback) | This call will return the results of a connectivity check. | Yes |
iapRunAdapterBasicGet(callback) | This call will return the results of running basic get API calls. | Yes |
iapMoveAdapterEntitiesToDB(callback) | This call will push the adapter configuration from the entities directory into the Adapter or IAP Database. | Yes |
iapDeactivateTasks(tasks, callback) | This call provides the ability to remove tasks from the adapter. | Yes |
iapActivateTasks(tasks, callback) | This call provides the ability to add deactivated tasks back into the adapter. | Yes |
iapExpandedGenericAdapterRequest(metadata, uriPath, restMethod, pathVars, queryData, requestBody, addlHeaders, callback) | This is an expanded Generic Call. The metadata object allows us to provide many new capabilities within the generic request. | Yes |
genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback) | This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet. | Yes |
genericAdapterRequestNoBasePath(uriPath, restMethod, queryData, requestBody, addlHeaders, callback) | This call is the same as the genericAdapterRequest only it does not add a base_path or version to the call. | Yes |
iapRunAdapterLint(callback) | Runs lint on the addapter and provides the information back. | Yes |
iapRunAdapterTests(callback) | Runs baseunit and unit tests on the adapter and provides the information back. | Yes |
iapGetAdapterInventory(callback) | This call provides some inventory related information about the adapter. | Yes |
Adapter Cache Calls
These are adapter methods that are used for adapter caching. If configured, the adapter will cache based on the interval provided. However, you can force a population of the cache manually as well.
Method Signature | Description | Workflow? |
---|---|---|
iapPopulateEntityCache(entityTypes, callback) | This call populates the adapter cache. | Yes |
iapRetrieveEntitiesCache(entityType, options, callback) | This call retrieves the specific items from the adapter cache. | Yes |
Adapter Broker Calls
These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
Method Signature | Description | Workflow? |
---|---|---|
hasEntities(entityType, entityList, callback) | This call is utilized by the IAP Device Broker to determine if the adapter has a specific entity and item of the entity. | No |
getDevice(deviceName, callback) | This call returns the details of the requested device. | No |
getDevicesFiltered(options, callback) | This call returns the list of devices that match the criteria provided in the options filter. | No |
isAlive(deviceName, callback) | This call returns whether the device status is active | No |
getConfig(deviceName, format, callback) | This call returns the configuration for the selected device. | No |
iapGetDeviceCount(callback) | This call returns the count of devices. | No |
Specific Adapter Calls
Specific adapter calls are built based on the API of the BlueCat. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.
Method Signature | Description | Path | Workflow? |
---|---|---|---|
addACL(configurationId, name, properties, callback) | Adds an Access Control List (ACL) to a view. | {base_path}/{version}/v1/addACL?{query} | Yes |
addAliasRecord(absoluteName, linkedRecordName, properties, ttl, viewId, callback) | Adds alias records. | {base_path}/{version}/v1/addAliasRecord?{query} | Yes |
addBulkHostRecord(absoluteName, networkId, numberOfAddresses, properties, startAddress, ttl, viewId, callback) | Adds bulk host records using auto-increment from the specific starting address. | {base_path}/{version}/v1/addBulkHostRecord?{query} | Yes |
addDNSDeploymentOption(entityId, name, properties, value, callback) | Adds DNS options. | {base_path}/{version}/v1/addDNSDeploymentOption?{query} | Yes |
addEnumNumber(enumZoneId, number, properties, callback) | Adds ENUM numbers. | {base_path}/{version}/v1/addEnumNumber?{query} | Yes |
addEnumZone(parentId, prefix, properties, callback) | Adds ENUM zones. | {base_path}/{version}/v1/addEnumZone?{query} | Yes |
addExternalHostRecord(name, properties, viewId, callback) | Adds external host records. | {base_path}/{version}/v1/addExternalHostRecord?{query} | Yes |
addGenericRecord(absoluteName, properties, rdata, ttl, type, viewId, callback) | Adds generic records. | {base_path}/{version}/v1/addGenericRecord?{query} | Yes |
addHINFORecord(absoluteName, cpu, os, properties, ttl, viewId, callback) | Adds HINFO records. | {base_path}/{version}/v1/addHINFORecord?{query} | Yes |
addHostRecord(absoluteName, addresses, properties, ttl, viewId, callback) | Adds host records for IPv4 or IPv6 addresses. | {base_path}/{version}/v1/addHostRecord?{query} | Yes |
addMXRecord(absoluteName, linkedRecordName, priority, properties, ttl, viewId, callback) | Adds MX records. | {base_path}/{version}/v1/addMXRecord?{query} | Yes |
addNAPTRRecord(absoluteName, flags, order, preference, properties, regexp, replacement, service, ttl, viewId, callback) | Adds NAPTR records. | {base_path}/{version}/v1/addNAPTRRecord?{query} | Yes |
addResourceRecord(absoluteName, properties, rdata, ttl, type, viewId, callback) | Add resource records. | {base_path}/{version}/v1/addResourceRecord?{query} | Yes |
addResponsePolicy(configurationId, name, properties, responsePolicyType, ttl, callback) | Adds a DNS response policy. | {base_path}/{version}/v1/addResponsePolicy?{query} | Yes |
addResponsePolicyItem(itemName, options, policyId, callback) | Adds a DNS response policy item under a specified local DNS response policy. | {base_path}/{version}/v1/addResponsePolicyItem?{query} | Yes |
addSRVRecord(absoluteName, linkedRecordName, port, priority, properties, ttl, viewId, weight, callback) | Adds SRV records. | {base_path}/{version}/v1/addSRVRecord?{query} | Yes |
addStartOfAuthority(email, expire, minimum, parentId, properties, refresh, retry, callback) | Adds SOA records. | {base_path}/{version}/v1/addStartOfAuthority?{query} | Yes |
addTXTRecord(absoluteName, properties, ttl, txt, viewId, callback) | Adds TXT records. | {base_path}/{version}/v1/addTXTRecord?{query} | Yes |
addView(configurationId, name, properties, callback) | Adds DNS views. | {base_path}/{version}/v1/addView?{query} | Yes |
addZone(absoluteName, parentId, properties, callback) | Adds DNS zones. | {base_path}/{version}/v1/addZone?{query} | Yes |
addZoneTemplate(name, parentId, properties, callback) | Adds a DNS zone template. | {base_path}/{version}/v1/addZoneTemplate?{query} | Yes |
deleteDNSDeploymentOption(entityId, name, serverId, callback) | Deletes DNS options. | {base_path}/{version}/v1/deleteDNSDeploymentOption?{query} | Yes |
deleteResponsePolicyItem(itemName, options, policyId, callback) | Deletes a DNS response policy item under a specified local DNS response policy. | {base_path}/{version}/v1/deleteResponsePolicyItem?{query} | Yes |
findResponsePoliciesWithItem(configurationId, itemName, options, callback) | Finds local DNS response policies with their associated response policy items. | {base_path}/{version}/v1/findResponsePoliciesWithItem?{query} | Yes |
getDNSDeploymentOption(entityId, name, serverId, callback) | Retrieves all DNS options assigned for the object specified excluding the options inherited from th | {base_path}/{version}/v1/getDNSDeploymentOption?{query} | Yes |
getHostRecordsByHint(count, options, start, callback) | Returns an array of objects with host record type. | {base_path}/{version}/v1/getHostRecordsByHint?{query} | Yes |
getKSK(entityId, format, callback) | Returns a string containing all active Key Signing Keys (KSK) for a given entityId value in a speci | {base_path}/{version}/v1/getKSK?{query} | Yes |
getNetworkLinkedProperties(networkId, callback) | Returns an array of IP addresses with linked records and the IP addresses that are assigned as DHCP | {base_path}/{version}/v1/getNetworkLinkedProperties?{query} | Yes |
getZonesByHint(containerId, count, options, start, callback) | Returns an array of accessible zones of child objects for a given containerId value. | {base_path}/{version}/v1/getZonesByHint?{query} | Yes |
moveResourceRecord(destinationZone, resourceRecordId, callback) | Moves resource records between different zones that already exist. | {base_path}/{version}/v1/moveResourceRecord?{query} | Yes |
searchResponsePolicyItems(count, keyword, properties, scope, start, callback) | Searches Response Policy items configured in local Response Policies or predefined BlueCat Security | {base_path}/{version}/v1/searchResponsePolicyItems?{query} | Yes |
updateDNSDeploymentOption(body, callback) | Updates DNS options. | {base_path}/{version}/v1/updateDNSDeploymentOption?{query} | Yes |
uploadResponsePolicyItems(inputStream, parentId, body, callback) | Uploads one response policy file containing a list of fully qualified domain names (FQDNs). | {base_path}/{version}/v1/uploadResponsePolicyItems?{query} | Yes |
addAccessRight(entityId, overrides, properties, userId, value, callback) | Adds access rights to a specified object. | {base_path}/{version}/v1/addAccessRight?{query} | Yes |
addDevice(configurationId, deviceSubtypeId, deviceTypeId, ip4Addresses, ip6Addresses, name, properties, callback) | Adds a device to a configuration. | {base_path}/{version}/v1/addDevice?{query} | Yes |
addDeviceSubtype(name, parentId, properties, callback) | Adds a device sub-type to Address Manager. | {base_path}/{version}/v1/addDeviceSubtype?{query} | Yes |
addDeviceType(name, properties, callback) | Adds a device type to Address Manager. | {base_path}/{version}/v1/addDeviceType?{query} | Yes |
addMACAddress(configurationId, macAddress, properties, callback) | Adds MAC addresses. | {base_path}/{version}/v1/addMACAddress?{query} | Yes |
addTag(name, parentId, properties, callback) | Adds object tags. | {base_path}/{version}/v1/addTag?{query} | Yes |
addTagGroup(name, properties, callback) | Adds object tag groups. | {base_path}/{version}/v1/addTagGroup?{query} | Yes |
addUser(password, properties, username, callback) | Adds Address Manager users. | {base_path}/{version}/v1/addUser?{query} | Yes |
addUserGroup(name, properties, callback) | Adds user groups. | {base_path}/{version}/v1/addUserGroup?{query} | Yes |
associateMACAddressWithPool(configurationId, macAddress, poolId, callback) | Associates a MAC address with a MAC pool. | {base_path}/{version}/v1/associateMACAddressWithPool?{query} | Yes |
breakReplication(callback) | Breaks replication and returns each server to its original stand-alone state. | {base_path}/{version}/v1/breakReplication?{query} | Yes |
configureStreamingReplication(compressReplication, latencyCriticalThreshold, latencyWarningThreshold, properties, standbyServer, callback) | Enables database replication on a remote system in order to automate the setup of replication betwe | {base_path}/{version}/v1/configureStreamingReplication?{query} | Yes |
deleteAccessRight(entityId, userId, callback) | Deletes an access right for a specified object. | {base_path}/{version}/v1/deleteAccessRight?{query} | Yes |
denyMACAddress(configurationId, macAddress, callback) | Denies MAC addresses. | {base_path}/{version}/v1/denyMACAddress?{query} | Yes |
establishTrustRelationship(password, properties, remoteIP, username, callback) | Establishes a trust relationship between a maximum of three Address Manager servers, which is a pre | {base_path}/{version}/v1/establishTrustRelationship?{query} | Yes |
failoverReplication(properties, standbyServer, callback) | Performs a manual replication failover. | {base_path}/{version}/v1/failoverReplication?{query} | Yes |
getAccessRight(entityId, userId, callback) | Retrieves an access right for a specified object. | {base_path}/{version}/v1/getAccessRight?{query} | Yes |
getAccessRightsForEntity(count, entityId, start, callback) | Returns an array of access rights for entities. | {base_path}/{version}/v1/getAccessRightsForEntity?{query} | Yes |
getAccessRightsForUser(count, start, userId, callback) | Returns an array of access rights for a specified user. | {base_path}/{version}/v1/getAccessRightsForUser?{query} | Yes |
getAllUsedLocations(callback) | Returns a list of location objects that are used to annotate other objects. | {base_path}/{version}/v1/getAllUsedLocations?{query} | Yes |
getConfigurationGroups(callback) | Gets a list of all configuration groups in Address Manager. | {base_path}/{version}/v1/getConfigurationGroups?{query} | Yes |
getConfigurationSetting(configurationId, settingName, callback) | Returns the configuration setting. | {base_path}/{version}/v1/getConfigurationSetting?{query} | Yes |
getConfigurationsByGroup(groupName, properties, callback) | Gets a list of configurations in Address Manager based on the name of a configuration group. | {base_path}/{version}/v1/getConfigurationsByGroup?{query} | Yes |
getLocationByCode(code, callback) | Returns the location object with the specified hierarchical location code. | {base_path}/{version}/v1/getLocationByCode?{query} | Yes |
getMACAddress(configurationId, macAddress, callback) | Returns an APIEntity for a MAC address. | {base_path}/{version}/v1/getMACAddress?{query} | Yes |
getReplicationInfo(properties, callback) | Retrieves information regarding the status of replication in Address Manager through the API. | {base_path}/{version}/v1/getReplicationInfo?{query} | Yes |
purgeHistoryNow(numberOfDaysToKeep, numberOfMonthsToKeep, untilWhenTimestamp, waitOption, callback) | Runs the history purge function. | {base_path}/{version}/v1/purgeHistoryNow?{query} | Yes |
removeTrustRelationship(otherBAMIP, properties, callback) | Removes a remote Address Manager server from the trust relationship. | {base_path}/{version}/v1/removeTrustRelationship?{query} | Yes |
terminateUserSessions(properties, username, callback) | Terminates all active user sessions in Address Manager. | {base_path}/{version}/v1/terminateUserSessions?{query} | Yes |
updateAccessRight(entityId, overrides, properties, userId, value, callback) | Updates access rights for a specified object. | {base_path}/{version}/v1/updateAccessRight?{query} | Yes |
updateConfigurationSetting(configurationId, properties, settingName, callback) | Updates the configuration setting. | {base_path}/{version}/v1/updateConfigurationSetting?{query} | Yes |
updateUserPassword(newPassword, options, userId, callback) | Updates an Address Manager user password. | {base_path}/{version}/v1/updateUserPassword?{query} | Yes |
addAdditionalIPAddresses(ipsToAdd, properties, serverId, callback) | Adds additional IPv4 addresses and loopback addresses to the Services interface for DNS service. | {base_path}/{version}/v1/addAdditionalIPAddresses?{query} | Yes |
addDeviceInstance(configName, deviceName, ipAddressMode, ipEntity, macAddressMode, macEntity, options, recordName, viewName, zoneName, callback) | Adds a device instance. | {base_path}/{version}/v1/addDeviceInstance?{query} | Yes |
addIP4BlockByCIDR(cIDR, parentId, properties, callback) | Adds a new IPv4 Block using CIDR notation. | {base_path}/{version}/v1/addIP4BlockByCIDR?{query} | Yes |
addIP4BlockByRange(end, parentId, properties, start, callback) | Adds a new IPv4 block defined by an address range. | {base_path}/{version}/v1/addIP4BlockByRange?{query} | Yes |
addIP4IPGroupByRange(end, name, parentId, properties, start, callback) | Adds an IPv4 IP group by range bounds (start address and end address). | {base_path}/{version}/v1/addIP4IPGroupByRange?{query} | Yes |
addIP4IPGroupBySize(name, parentId, positionRangeBy, positionValue, properties, size, callback) | Adds an IPv4 IP group by size. | {base_path}/{version}/v1/addIP4IPGroupBySize?{query} | Yes |
addIP4Network(cIDR, blockId, properties, callback) | Adds an IPv4 network using CIDR notation. | {base_path}/{version}/v1/addIP4Network?{query} | Yes |
addIP4NetworkTemplate(configurationId, name, properties, callback) | Add an IPv4 network template to the specified configuration. | {base_path}/{version}/v1/addIP4NetworkTemplate?{query} | Yes |
addIP4ReconciliationPolicy(name, parentId, properties, callback) | Adds an IPv4 reconciliation policy. | {base_path}/{version}/v1/addIP4ReconciliationPolicy?{query} | Yes |
addIP6Address(address, containerId, name, properties, type, callback) | Adds an IPv6 address to a specified IPv6 network. | {base_path}/{version}/v1/addIP6Address?{query} | Yes |
addIP6BlockByMACAddress(macAddress, name, parentId, properties, callback) | Adds an IPv6 block by specifying the MAC address of the server. | {base_path}/{version}/v1/addIP6BlockByMACAddress?{query} | Yes |
addIP6BlockByPrefix(name, parentId, prefix, properties, callback) | Adds an IPv6 block be specifying the prefix for the block. | {base_path}/{version}/v1/addIP6BlockByPrefix?{query} | Yes |
addIP6NetworkByPrefix(name, parentId, prefix, properties, callback) | Adds an IPv6 network be specifying the prefix for the network. | {base_path}/{version}/v1/addIP6NetworkByPrefix?{query} | Yes |
addParentBlock(body, callback) | Adds a parent block. | {base_path}/{version}/v1/addParentBlock?{query} | Yes |
addParentBlockWithProperties(properties, body, callback) | Adds a parent block with properties. | {base_path}/{version}/v1/addParentBlockWithProperties?{query} | Yes |
applyIP4NetworkTemplate(networkId, properties, templateId, callback) | Applies IPv4 network templates. | {base_path}/{version}/v1/applyIP4NetworkTemplate?{query} | Yes |
assignIP4Address(action, configurationId, hostInfo, ip4Address, macAddress, properties, callback) | Assigns a MAC address and other properties to an IPv4 address. | {base_path}/{version}/v1/assignIP4Address?{query} | Yes |
assignIP4NetworkTemplate(networkId, properties, templateId, callback) | Assigns IPv4 network templates. | {base_path}/{version}/v1/assignIP4NetworkTemplate?{query} | Yes |
assignIP6Address(action, address, containerId, hostInfo, macAddress, properties, callback) | Assigns an IPv6 address to a MAC address and host. | {base_path}/{version}/v1/assignIP6Address?{query} | Yes |
assignNextAvailableIP4Address(action, configurationId, hostInfo, macAddress, parentId, properties, callback) | Assign the next available IPv4 address. | {base_path}/{version}/v1/assignNextAvailableIP4Address?{query} | Yes |
changeStateIP4Address(addressId, macAddress, targetState, callback) | Converts the state of an address from and between Reserved, DHCP Reserved, and Static, or DHCP Allo | {base_path}/{version}/v1/changeStateIP4Address?{query} | Yes |
clearIP6Address(addressId, callback) | Clears a specified IPv6 address assignment. | {base_path}/{version}/v1/clearIP6Address?{query} | Yes |
deleteDeviceInstance(configName, identifier, options, callback) | Deletes either the IP address or MAC address (and all related DNS entries including host records, P | {base_path}/{version}/v1/deleteDeviceInstance?{query} | Yes |
getAdditionalIPAddresses(adonisID, properties, callback) | Returns IPv4 addresses and loopback addresses added to the Service interface for DNS services. | {base_path}/{version}/v1/getAdditionalIPAddresses?{query} | Yes |
getAliasesByHint(count, options, start, callback) | Returns an array of CNAMEs with linked record name. | {base_path}/{version}/v1/getAliasesByHint?{query} | Yes |
getDiscoveredDevice(deviceId, policyId, callback) | Returns the object ID of the discovered device by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDevice?{query} | Yes |
getDiscoveredDeviceArpEntries(deviceId, policyId, callback) | Returns all ARP entries of a specific device discovered by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDeviceArpEntries?{query} | Yes |
getDiscoveredDeviceHosts(deviceId, policyId, callback) | Returns all hosts of a specific device discovered by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDeviceHosts?{query} | Yes |
getDiscoveredDeviceInterfaces(deviceId, policyId, callback) | Returns all interfaces of a specific device discovered by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDeviceInterfaces?{query} | Yes |
getDiscoveredDeviceMacAddressEntries(deviceId, policyId, callback) | Returns all MAC address entries of a specific device discovered by running an IPv4 reconciliation p | {base_path}/{version}/v1/getDiscoveredDeviceMacAddressEntries?{query} | Yes |
getDiscoveredDeviceNetworks(deviceId, policyId, callback) | Returns all networks of a specific device discovered by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDeviceNetworks?{query} | Yes |
getDiscoveredDeviceVlans(deviceId, policyId, callback) | Returns all VLANs of a specific device discovered by running an IPv4 reconciliation policy. | {base_path}/{version}/v1/getDiscoveredDeviceVlans?{query} | Yes |
getDiscoveredDevices(policyId, callback) | Returns a list of discovered Layer 2 or Layer 3 devices by running an IPv4 reconciliation policy sp | {base_path}/{version}/v1/getDiscoveredDevices?{query} | Yes |
getIP4Address(address, containerId, callback) | Returns the details for the requested IPv4 address object. | {base_path}/{version}/v1/getIP4Address?{query} | Yes |
getIP4NetworksByHint(containerId, count, options, start, callback) | Returns an array of IPv4 networks found under a given container object. | {base_path}/{version}/v1/getIP4NetworksByHint?{query} | Yes |
getIP6Address(address, containerId, callback) | Returns an APIEntity for the specified IPv6 address. | {base_path}/{version}/v1/getIP6Address?{query} | Yes |
getIP6ObjectsByHint(containerId, count, objectType, options, start, callback) | Returns an array of IPv6 objects found under a given container object. | {base_path}/{version}/v1/getIP6ObjectsByHint?{query} | Yes |
getIPRangedByIP(address, containerId, type, callback) | Returns the DHCP range containing the specified IPv4 or IPv6 address. | {base_path}/{version}/v1/getIPRangedByIP?{query} | Yes |
getLinkedNetworkConflicts(networkId, templateId, callback) | Get a list of deployment options that conflict with the associated networks or network that are lin | {base_path}/{version}/v1/getLinkedNetworkConflicts?{query} | Yes |
getMaxAllowedRange(rangeId, callback) | Finds the maximum possible address range to which the existing IPv4 DHCP range can be extended. | {base_path}/{version}/v1/getMaxAllowedRange?{query} | Yes |
getNextAvailableIP4Address(parentId, callback) | Returns the IPv4 address for the next available (unallocated) address within a configuration, block | {base_path}/{version}/v1/getNextAvailableIP4Address?{query} | Yes |
getNextAvailableIP4Network(autoCreate, isLargerAllowed, parentId, size, callback) | Returns the object ID for the next available (unused) network within a configuration or block. | {base_path}/{version}/v1/getNextAvailableIP4Network?{query} | Yes |
getNextAvailableIP6Address(parentId, properties, callback) | Returns the next available IPv6 address within an IPv6 block or network. | {base_path}/{version}/v1/getNextAvailableIP6Address?{query} | Yes |
getNextAvailableIPRange(parentId, properties, size, type, callback) | Returns the object ID for the next available (unused) block or network within a configuration or bl | {base_path}/{version}/v1/getNextAvailableIPRange?{query} | Yes |
getNextAvailableIPRanges(count, parentId, properties, size, type, callback) | Returns the object IDs for the next available (unused) blocks or networks within a configuration or | {base_path}/{version}/v1/getNextAvailableIPRanges?{query} | Yes |
getNextIP4Address(parentId, properties, callback) | Returns the next available IP addresses in octet notation under specified circumstances. | {base_path}/{version}/v1/getNextIP4Address?{query} | Yes |
getTemplateTaskStatus(taskId, callback) | Gets the IPv4 template task status when the template is applied. | {base_path}/{version}/v1/getTemplateTaskStatus?{query} | Yes |
isAddressAllocated(configurationId, ipAddress, macAddress, callback) | Queries a MAC address to determine if the address has been allocated to an IP address. | {base_path}/{version}/v1/isAddressAllocated?{query} | Yes |
mergeBlocksWithParent(body, callback) | Merges specified IPv4 blocks into a single block. | {base_path}/{version}/v1/mergeBlocksWithParent?{query} | Yes |
mergeSelectedBlocksOrNetworks(blockOrNetworkToKeep, body, callback) | Merges specified IPv4 blocks or IPv4 networks into a single IPv4 block or IPv4 network. | {base_path}/{version}/v1/mergeSelectedBlocksOrNetworks?{query} | Yes |
moveIPObject(address, objectId, options, callback) | Moves an IPv4 block, IPv4 network, IPv4 address, IPv6 block, or IPv6 network to a new IPv4 or IPv6 | {base_path}/{version}/v1/moveIPObject?{query} | Yes |
reapplyTemplate(properties, templateId, callback) | Reapplies DNS zone templates. | {base_path}/{version}/v1/reapplyTemplate?{query} | Yes |
reassignIP6Address(destination, oldAddressId, properties, callback) | Reassigns an existing IPv6 address to a new IPv6 address. | {base_path}/{version}/v1/reassignIP6Address?{query} | Yes |
removeAdditionalIPAddresses(ipsToRemove, properties, serverId, callback) | Removes additional IPv4 addresses and loopback addresses from the Services interface. | {base_path}/{version}/v1/removeAdditionalIPAddresses?{query} | Yes |
resizeRange(objectId, options, range, callback) | Changes the size of an IPv4 block, IPv4 network, DHCPv4 range, IPv6 block, or IPv6 network. | {base_path}/{version}/v1/resizeRange?{query} | Yes |
splitIP4Network(networkId, numberOfParts, options, callback) | Splits an IPv4 network into the specified number of networks. | {base_path}/{version}/v1/splitIP4Network?{query} | Yes |
splitIP6Range(numberOfParts, options, rangeId, callback) | Splits an IPv6 block or network into the specified number of blocks or networks. | {base_path}/{version}/v1/splitIP6Range?{query} | Yes |
unassignIP4NetworkTemplate(networkId, properties, templateId, callback) | Unassigns IPv4 network templates. | {base_path}/{version}/v1/unassignIP4NetworkTemplate?{query} | Yes |
addCustomOptionDefinition(allowMultiple, configurationId, name, optionId, optionType, properties, callback) | Adds a custom deployment option. | {base_path}/{version}/v1/addCustomOptionDefinition?{query} | Yes |
addDHCP4Range(end, networkId, properties, start, callback) | Adds IPv4 DHCP ranges. | {base_path}/{version}/v1/addDHCP4Range?{query} | Yes |
addDHCP4RangeBySize(networkId, offset, properties, size, callback) | Adds IPv4 DHCP ranges by offset and percentage. | {base_path}/{version}/v1/addDHCP4RangeBySize?{query} | Yes |
addDHCP6ClientDeploymentOption(entityId, name, properties, value, callback) | Adds DHCPv6 client options and returns the database object ID for the new option object. | {base_path}/{version}/v1/addDHCP6ClientDeploymentOption?{query} | Yes |
addDHCP6Range(end, networkId, properties, start, callback) | Adds IPv6 DHCP ranges. | {base_path}/{version}/v1/addDHCP6Range?{query} | Yes |
addDHCP6RangeBySize(networkId, properties, size, start, callback) | Adds IPv6 DHCP ranges by size. | {base_path}/{version}/v1/addDHCP6RangeBySize?{query} | Yes |
addDHCP6ServiceDeploymentOption(entityId, name, properties, value, callback) | Adds DHCPv6 service options. | {base_path}/{version}/v1/addDHCP6ServiceDeploymentOption?{query} | Yes |
addDHCPClientDeploymentOption(entityId, name, properties, value, callback) | Adds a DHCP client option and returns the object ID for the new option object. | {base_path}/{version}/v1/addDHCPClientDeploymentOption?{query} | Yes |
addDHCPMatchClass(configurationId, matchCriteria, name, properties, callback) | Adds DHCP match classes to Address Manager. | {base_path}/{version}/v1/addDHCPMatchClass?{query} | Yes |
addDHCPServiceDeploymentOption(entityId, name, properties, value, callback) | Adds DHCP service options. | {base_path}/{version}/v1/addDHCPServiceDeploymentOption?{query} | Yes |
addDHCPSubClass(matchClassId, matchValue, properties, callback) | Adds DHCP match class values. | {base_path}/{version}/v1/addDHCPSubClass?{query} | Yes |
addDHCPVendorDeploymentOption(optionId, parentId, properties, value, callback) | Adds a DHCP vendor deployment option to specified objects. | {base_path}/{version}/v1/addDHCPVendorDeploymentOption?{query} | Yes |
addVendorOptionDefinition(allowMultiple, description, name, optionId, optionType, properties, vendorProfileId, callback) | Adds a vendor option definition to a vendor profile. | {base_path}/{version}/v1/addVendorOptionDefinition?{query} | Yes |
addVendorProfile(description, identifier, name, properties, callback) | Adds a vendor profile and returns the object ID for the new vendor profile. | {base_path}/{version}/v1/addVendorProfile?{query} | Yes |
deleteDHCP6ClientDeploymentOption(entityId, name, serverId, callback) | Deletes DHCPv6 client options. | {base_path}/{version}/v1/deleteDHCP6ClientDeploymentOption?{query} | Yes |
deleteDHCP6ServiceDeploymentOption(entityId, name, serverId, callback) | Deletes DHCPv6 service options. | {base_path}/{version}/v1/deleteDHCP6ServiceDeploymentOption?{query} | Yes |
deleteDHCPClientDeploymentOption(entityId, name, serverId, callback) | Deletes DHCP client options. | {base_path}/{version}/v1/deleteDHCPClientDeploymentOption?{query} | Yes |
deleteDHCPServiceDeploymentOption(entityId, name, serverId, callback) | Deletes DHCP service options. | {base_path}/{version}/v1/deleteDHCPServiceDeploymentOption?{query} | Yes |
deleteDHCPVendorDeploymentOption(entityId, optionId, serverId, callback) | Deletes a specified DHCP vendor deployment option. | {base_path}/{version}/v1/deleteDHCPVendorDeploymentOption?{query} | Yes |
getDHCP6ClientDeploymentOption(entityId, name, serverId, callback) | Returns DHCPv6 client options assigned for the object specified excluding the options inherited fro | {base_path}/{version}/v1/getDHCP6ClientDeploymentOption?{query} | Yes |
getDHCP6ServiceDeploymentOption(entityId, name, serverId, callback) | Returns DHCPv6 service options assigned for the object specified excluding the options inherited fr | {base_path}/{version}/v1/getDHCP6ServiceDeploymentOption?{query} | Yes |
getDHCPClientDeploymentOption(entityId, name, serverId, callback) | Returns DHCPv4 client options assigned for the object specified excluding the options inherited fro | {base_path}/{version}/v1/getDHCPClientDeploymentOption?{query} | Yes |
getDHCPServiceDeploymentOption(entityId, name, serverId, callback) | Returns DHCP service options assigned for the object specified excluding the options inherited from | {base_path}/{version}/v1/getDHCPServiceDeploymentOption?{query} | Yes |
getDHCPVendorDeploymentOption(entityId, optionId, serverId, callback) | Retrieves a DHCP vendor deployment option assigned for the object specified excluding the options i | {base_path}/{version}/v1/getDHCPVendorDeploymentOption?{query} | Yes |
getSharedNetworks(tagId, callback) | Returns multiple IPv4 networks linked to the given shared network tag. | {base_path}/{version}/v1/getSharedNetworks?{query} | Yes |
shareNetwork(networkId, tagId, callback) | Links an IPv4 network with a shared network tag. | {base_path}/{version}/v1/shareNetwork?{query} | Yes |
unshareNetwork(networkId, callback) | Unlinks the shared network tag from an IPv4 network. | {base_path}/{version}/v1/unshareNetwork?{query} | Yes |
updateDHCP6ClientDeploymentOption(body, callback) | Updates DHCPv6 client options. | {base_path}/{version}/v1/updateDHCP6ClientDeploymentOption?{query} | Yes |
updateDHCP6ServiceDeploymentOption(body, callback) | Updates DHCPv6 service options. | {base_path}/{version}/v1/updateDHCP6ServiceDeploymentOption?{query} | Yes |
updateDHCPClientDeploymentOption(body, callback) | Updates DHCP client options. | {base_path}/{version}/v1/updateDHCPClientDeploymentOption?{query} | Yes |
updateDHCPServiceDeploymentOption(body, callback) | Updates DHCP service options. | {base_path}/{version}/v1/updateDHCPServiceDeploymentOption?{query} | Yes |
updateDHCPVendorDeploymentOption(body, callback) | Updates the specified DHCP vendor deployment option. | {base_path}/{version}/v1/updateDHCPVendorDeploymentOption?{query} | Yes |
addDHCPDeploymentRole(entityId, properties, serverInterfaceId, type, callback) | Adds a DHCP deployment role to a specified object. | {base_path}/{version}/v1/addDHCPDeploymentRole?{query} | Yes |
addDNSDeploymentRole(entityId, properties, serverInterfaceId, type, callback) | Adds a DNS deployment role to a specified object. | {base_path}/{version}/v1/addDNSDeploymentRole?{query} | Yes |
addServer(configurationId, defaultInterfaceAddress, fullHostName, name, profile, properties, callback) | Adds servers to Address Manager. | {base_path}/{version}/v1/addServer?{query} | Yes |
addTFTPDeploymentRole(entityId, properties, serverId, callback) | Adds a TFTP deployment role to a specified object. | {base_path}/{version}/v1/addTFTPDeploymentRole?{query} | Yes |
deleteDHCPDeploymentRole(entityId, serverInterfaceId, callback) | Deletes DHCP deployment roles. | {base_path}/{version}/v1/deleteDHCPDeploymentRole?{query} | Yes |
deleteDNSDeploymentRole(entityId, serverInterfaceId, callback) | Deletes a specified DNS deployment role. | {base_path}/{version}/v1/deleteDNSDeploymentRole?{query} | Yes |
deleteDNSDeploymentRoleForView(entityId, serverInterfaceId, viewId, callback) | Deletes the DNS deployment role assigned to view-level objects in the IP space for ARPA zones. | {base_path}/{version}/v1/deleteDNSDeploymentRoleForView?{query} | Yes |
deployServer(serverId, callback) | Deploys servers. | {base_path}/{version}/v1/deployServer?{query} | Yes |
deployServerConfig(properties, serverId, callback) | Deploys specific configuration(s) to a particular server. | {base_path}/{version}/v1/deployServerConfig?{query} | Yes |
deployServerServices(serverId, services, callback) | Deploys specific service(s) to a particular server. | {base_path}/{version}/v1/deployServerServices?{query} | Yes |
getDHCPDeploymentRole(entityId, serverInterfaceId, callback) | Retrieves the DHCP deployment role assigned to a specified object. | {base_path}/{version}/v1/getDHCPDeploymentRole?{query} | Yes |
getDNSDeploymentRole(entityId, serverInterfaceId, callback) | Retrieves a DNS deployment role from a specified object. | {base_path}/{version}/v1/getDNSDeploymentRole?{query} | Yes |
getDNSDeploymentRoleForView(entityId, serverInterfaceId, viewId, callback) | Retrieves the DNS deployment role assigned to a view-level objects in the IP space for ARPA zones. | {base_path}/{version}/v1/getDNSDeploymentRoleForView?{query} | Yes |
getDeploymentRoles(entityId, callback) | Returns the DNS and DHCP deployment roles associated with the specified object. | {base_path}/{version}/v1/getDeploymentRoles?{query} | Yes |
getDeploymentTaskStatus(deploymentTaskToken, callback) | Returns the deployment status of the deployment task that was created using the. | {base_path}/{version}/v1/getDeploymentTaskStatus?{query} | Yes |
getServerDeploymentRoles(serverId, callback) | Returns a list of all deployment roles associated with the server. | {base_path}/{version}/v1/getServerDeploymentRoles?{query} | Yes |
getServerDeploymentStatus(properties, serverId, callback) | Returns the deployment status of the server. | {base_path}/{version}/v1/getServerDeploymentStatus?{query} | Yes |
getServerForRole(roleId, callback) | Returns a list of all servers associated with the specified deployment role. | {base_path}/{version}/v1/getServerForRole?{query} | Yes |
moveDeploymentRoles(moveDhcpRoles, moveDnsRoles, options, sourceServerId, targetServerInterfaceId, callback) | Moves all DNS and DHCP deployment roles from a server to the specified interface of another server. | {base_path}/{version}/v1/moveDeploymentRoles?{query} | Yes |
quickDeploy(entityId, properties, callback) | Instantly deploys changes you made to DNS resource records since the last full or quick deployment. | {base_path}/{version}/v1/quickDeploy?{query} | Yes |
replaceServer(defaultInterface, hostName, name, password, properties, serverId, upgrade, callback) | Replaces a server. | {base_path}/{version}/v1/replaceServer?{query} | Yes |
selectiveDeploy(properties, body, callback) | Selectively deploys—creates a differential deployment task to deploy changes made to specific DNS e | {base_path}/{version}/v1/selectiveDeploy?{query} | Yes |
updateDHCPDeploymentRole(body, callback) | Updates a DHCP deployment role. | {base_path}/{version}/v1/updateDHCPDeploymentRole?{query} | Yes |
updateDNSDeploymentRole(body, callback) | Updates a specified DNS deployment role. | {base_path}/{version}/v1/updateDNSDeploymentRole?{query} | Yes |
addEntity(parentId, body, callback) | A generic method for adding configurations, DNS zones, and DNS resource records. | {base_path}/{version}/v1/addEntity?{query} | Yes |
assignOrUpdateTemplate(entityId, properties, templateId, callback) | Assigns, updates, or removes DNS zone and IPv4 network templates. | {base_path}/{version}/v1/assignOrUpdateTemplate?{query} | Yes |
customSearch(count, filters, options, start, type, callback) | Search for an array of entities by specifying object properties. | {base_path}/{version}/v1/customSearch?{query} | Yes |
delete(objectId, callback) | Deletes an object using the generic. | {base_path}/{version}/v1/delete?{query} | Yes |
deleteWithOptions(objectId, options, callback) | Deletes objects that have options associated with their removal. | {base_path}/{version}/v1/deleteWithOptions?{query} | Yes |
getEntities(count, parentId, start, type, callback) | Returns multiple entities for the specified parent ID. | {base_path}/{version}/v1/getEntities?{query} | Yes |
getEntitiesByName(count, name, parentId, start, type, callback) | Returns an array of entities that match the specified parent, name, and object type. | {base_path}/{version}/v1/getEntitiesByName?{query} | Yes |
getEntitiesByNameUsingOptions(count, name, options, parentId, start, type, callback) | Returns an array of entities that match the specified name and object type. | {base_path}/{version}/v1/getEntitiesByNameUsingOptions?{query} | Yes |
getEntityByCIDR(cidr, parentId, type, callback) | Returns an IPv4 Network object from the database by calling it using CIDR notation. | {base_path}/{version}/v1/getEntityByCIDR?{query} | Yes |
getEntityById(id, callback) | Returns objects from the database referenced by their database ID and with its properties fields po | {base_path}/{version}/v1/getEntityById?{query} | Yes |
getEntityByName(name, parentId, type, callback) | Returns objects from the database referenced by their name field. | {base_path}/{version}/v1/getEntityByName?{query} | Yes |
getEntityByPrefix(containerId, prefix, type, callback) | Returns an APIEntity for the specified IP block or network. | {base_path}/{version}/v1/getEntityByPrefix?{query} | Yes |
getEntityByRange(address1, address2, parentId, type, callback) | Returns an IPv4 DHCP range object by calling it using its range. | {base_path}/{version}/v1/getEntityByRange?{query} | Yes |
getLinkedEntities(count, entityId, start, type, callback) | Returns an array of entities containing the entities linked to a specified entity. | {base_path}/{version}/v1/getLinkedEntities?{query} | Yes |
getParent(entityId, callback) | Returns the parent entity of a given entity. | {base_path}/{version}/v1/getParent?{query} | Yes |
getSystemInfo(callback) | Gets Address Manager system information. | {base_path}/{version}/v1/getSystemInfo?{query} | Yes |
linkEntities(entity1Id, entity2Id, properties, callback) | Establishes a link between two specified Address Manager entities. | {base_path}/{version}/v1/linkEntities?{query} | Yes |
login(password, username, callback) | Logs in as API user. | {base_path}/{version}/v1/login?{query} | Yes |
loginWithOptions(options, password, username, callback) | Logs in as an API user with the option to change the locale to Japanese or Simplified Chinese. | {base_path}/{version}/v1/loginWithOptions?{query} | Yes |
logout(callback) | Logs out of the current API session. | {base_path}/{version}/v1/logout?{query} | Yes |
searchByCategory(category, count, keyword, start, callback) | Returns an array of entities by searching for keywords associated with objects of a specified objec | {base_path}/{version}/v1/searchByCategory?{query} | Yes |
searchByObjectTypes(count, keyword, start, types, callback) | Returns an array of entities by searching for keywords associated with objects of a specified objec | {base_path}/{version}/v1/searchByObjectTypes?{query} | Yes |
unlinkEntities(entity1Id, entity2Id, properties, callback) | Removes the link between two specified Address Manager entities. | {base_path}/{version}/v1/unlinkEntities?{query} | Yes |
update(body, callback) | Updates entity objects. | {base_path}/{version}/v1/update?{query} | Yes |
updateWithOptions(options, body, callback) | Updates objects requiring a certain behavior that is not covered by the regular. | {base_path}/{version}/v1/updateWithOptions?{query} | Yes |
addRawDeploymentOption(parentId, body, callback) | Adds raw deployment options. | {base_path}/{version}/v1/addRawDeploymentOption?{query} | Yes |
getDeploymentOptions(entityId, optionTypes, serverId, callback) | Retrieves deployment options for Address Manager DNS and DHCP services. | {base_path}/{version}/v1/getDeploymentOptions?{query} | Yes |
updateRawDeploymentOption(body, callback) | Updates raw deployment options. | {base_path}/{version}/v1/updateRawDeploymentOption?{query} | Yes |
addTFTPFile(inputStream, name, parentId, properties, version, body, callback) | Adds TFTP files. | {base_path}/{version}/v1/addTFTPFile?{query} | Yes |
addTFTPFolder(name, parentId, properties, callback) | Adds TFTP folders. | {base_path}/{version}/v1/addTFTPFolder?{query} | Yes |
addTFTPGroup(configurationId, name, properties, callback) | Adds TFTP groups. | {base_path}/{version}/v1/addTFTPGroup?{query} | Yes |
addUserDefinedField(type, body, callback) | Adds user-defined fields. | {base_path}/{version}/v1/addUserDefinedField?{query} | Yes |
deleteUserDefinedField(name, type, callback) | Deletes user-defined fields. | {base_path}/{version}/v1/deleteUserDefinedField?{query} | Yes |
getUserDefinedFields(requiredFieldsOnly, type, callback) | Returns the user-defined fields information. | {base_path}/{version}/v1/getUserDefinedFields?{query} | Yes |
updateBulkUdf(inputStream, properties, body, callback) | Updates values of various user-defined fields (UDFs) for different objects. | {base_path}/{version}/v1/updateBulkUdf?{query} | Yes |
updateUserDefinedField(type, body, callback) | Updates user-defined fields. | {base_path}/{version}/v1/updateUserDefinedField?{query} | Yes |
breakXHAPair(breakInProteusOnly, xHAServerId, callback) | Breaks an xHA pair and returns each server to its original stand-alone state. | {base_path}/{version}/v1/breakXHAPair?{query} | Yes |
createXHAPair(activeServerId, activeServerNewIPv4Address, configurationId, passiveServerId, properties, callback) | Creates an xHA pair. | {base_path}/{version}/v1/createXHAPair?{query} | Yes |
editXHAPair(name, properties, xHAServerId, callback) | Updates the xHA pair created. | {base_path}/{version}/v1/editXHAPair?{query} | Yes |
failoverXHA(xHAServerId, callback) | Performs a manual xHA failover. | {base_path}/{version}/v1/failoverXHA?{query} | Yes |
cleanBrokenTrustRelationship(ipsToRemove, callback) | This is an internal API used by Address Manager services. | {base_path}/{version}/v1/cleanBrokenTrustRelationship?{query} | Yes |
configureReplication(compressReplication, properties, replicationBreakThreshold, replicationQueueThreshold, standbyServer, callback) | This API has been deprecated and is no longer supported. | {base_path}/{version}/v1/configureReplication?{query} | Yes |
exchangeKeyBundles(body, callback) | This is an internal API used by Address Manager services. | {base_path}/{version}/v1/exchangeKeyBundles?{query} | Yes |
moveIP4Object(address, objectId, callback) | This API has been deprecated and is no longer supported. | {base_path}/{version}/v1/moveIP4Object?{query} | Yes |
getProbeData(definedProbe, properties, callback) | Returns the JSON response from the properties field of the APIData object. | {base_path}/{version}/v1/getProbeData?{query} | Yes |
getProbeStatus(definedProbe, callback) | Returns the status of the triggered data collection process. | {base_path}/{version}/v1/getProbeStatus?{query} | Yes |
startProbe(definedProbe, properties, callback) | Starts collecting data from the Address Manager database using pre-defined SQL queries. | {base_path}/{version}/v1/startProbe?{query} | Yes |
isMigrationRunning(filename, callback) | Returns true or false to indicate if the migration service is running. | {base_path}/{version}/v1/isMigrationRunning?{query} | Yes |
migrateFile(filename, callback) | Migrates the specified XML file into Address Manager. | {base_path}/{version}/v1/migrateFile?{query} | Yes |
Authentication
This document will go through the steps for authenticating the BlueCat adapter with the authentication methods we have worked with in the past. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication HERE.
Dynamic Token Authentication
The BlueCat adapter requires Dynamic Token Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
STEPS
- Ensure you have access to a BlueCat server and that it is running
- Follow the steps in the README.md to import the adapter into IAP if you have not already done so
- Use the properties below for the
properties.authentication
field"authentication": { "auth_method": "request_token", "username": "<username>", "password": "<password>", "token_timeout": 1800000, "token_cache": "local", "invalid_token_error": 401, "auth_field": "header.headers.Authorization", "auth_field_format": "{token}", "auth_logging": false, }
you can leave all of the other properties in the authentication section, they will not be used for BlueCat dynamic token authentication.
- Restart the adapter. If your properties were set correctly, the adapter should go online.
Troubleshooting
- Make sure you copied over the correct username and password.
- Turn on debug level logs for the adapter in IAP Admin Essentials.
- Turn on auth_logging for the adapter in IAP Admin Essentials (adapter properties).
- Investigate the logs - in particular:
- The FULL REQUEST log to make sure the proper headers are being sent with the request.
- The FULL BODY log to make sure the payload is accurate.
- The CALL RETURN log to see what the other system is telling us.
- Credentials should be masked by the adapter so make sure you verify the username and password - including that there are erroneous spaces at the front or end.
- Remember when you are done to turn auth_logging off as you do not want to log credentials.
Additional Information
Enhancements
Adding a Second Instance of an Adapter
You can add a second instance of this adapter without adding new code on the file system. To do this go into the IAP Admin Essentials and add a new service config for this adapter. The two instances of the adapter should have unique ids. In addition, they should point to different instances (unique host and port) of the other system.
Adding Adapter Calls
There are multiple ways to add calls to an existing adapter.
The easiest way would be to use the Adapter Builder update process. This process takes in a Swagger or OpenAPI document, allows you to select the calls you want to add and then generates a zip file that can be used to update the adapter. Once you have the zip file simply put it in the adapter directory and execute npm run adapter:update
.
mv updatePackage.zip adapter-bluecat
cd adapter-bluecat
npm run adapter:update
If you do not have a Swagger or OpenAPI document, you can use a Postman Collection and convert that to an OpenAPI document using APIMatic and then follow the first process.
If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the Adapter Technical Resources on our Documentation Site.
Files to update
* entities/<entity>/action.json: add an action
* entities/<entity>/schema.json (or the schema defined on the action): add action to the enum for ph_request_type
* adapter.js: add the new method and make sure it calls the proper entity and action
* pronghorn.json: add the new method
* test/unit/adapterTestUnit.js (optional but best practice): add unit test(s) - function is there, any required parameters error when not passed in
* test/integration/adapterTestIntegration.js (optional but best practice): add integration test
Adding Adapter Properties
While changing adapter properties is done in the service instance configuration section of IAP, adding properties has to be done in the adapter. To add a property you should edit the propertiesSchema.json with the proper information for the property. In addition, you should modify the sampleProperties to have the new property in it.
Files to update
* propertiesSchema.json: add the new property and how it is defined
* sampleProperties: add the new property with a default value
* test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
* test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
Changing Adapter Authentication
Often an adapter is built before knowing the authentication and authentication processes can also change over time. The adapter supports many different kinds of authentication but it does require configuration. Some forms of authentication can be defined entirely with the adapter properties but others require configuration.
Files to update
* entities/.system/action.json: change the getToken action as needed
* entities/.system/schemaTokenReq.json: add input parameters (external name is name in other system)
* entities/.system/schemaTokenResp.json: add response parameters (external name is name in other system)
* propertiesSchema.json: add any new property and how it is defined
* sampleProperties: add any new property with a default value
* test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
* test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
Enhancing Adapter Integration Tests
The adapter integration tests are written to be able to test in either stub (standalone) mode or integrated to the other system. However, if integrating to the other system, you may need to provide better data than what the adapter provides by default as that data is likely to fail for create and update. To provide better data, edit the adapter integration test file. Make sure you do not remove the marker and keep custom code below the marker so you do not impact future migrations. Once the edits are complete, run the integration test as it instructs you to above. When you run integrated to the other system, you can also save mockdata for future use by changing the isSaveMockData flag to true.
Files to update
* test/integration/adapterTestIntegration.js: add better data for the create and update calls so that they will not fail.
As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the Adapter Technical Resources on our Documentation Site.
Contributing
First off, thanks for taking the time to contribute!
The following is a set of rules for contributing.
Code of Conduct
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to support@itential.com.
How to Contribute
Follow the contributing guide (here)[https://gitlab.com/itentialopensource/adapters/contributing-guide]
Helpful Links
Node Scripts
There are several node scripts that now accompany the adapter. These scripts are provided to make several activities easier. Many of these scripts can have issues with different versions of IAP as they have dependencies on IAP and Mongo. If you have issues with the scripts please report them to the Itential Adapter Team. Each of these scripts are described below.
Run | Description |
---|---|
npm run adapter:install | Provides an easier way to install the adapter. |
npm run adapter:checkMigrate | Checks whether your adapter can and should be migrated to the latest foundation. |
npm run adapter:findPath | Can be used to see if the adapter supports a particular API call. |
npm run adapter:migrate | Provides an easier way to update your adapter after you download the migration zip from Itential DevSite. |
npm run adapter:update | Provides an easier way to update your adapter after you download the update zip from Itential DevSite. |
npm run adapter:revert | Allows you to revert after a migration or update if it resulted in issues. |
npm run troubleshoot | Provides a way to troubleshoot the adapter - runs connectivity, healthcheck and basic get. |
npm run connectivity | Provides a connectivity check to the Servicenow system. |
npm run healthcheck | Checks whether the configured healthcheck call works to Servicenow. |
npm run basicget | Checks whether the basic get calls works to Servicenow. |
Troubleshoot
Run npm run troubleshoot
to start the interactive troubleshooting process. The command allows you to verify and update connection, authentication as well as healthcheck configuration. After that it will test these properties by sending HTTP request to the endpoint. If the tests pass, it will persist these changes into IAP.
You also have the option to run individual commands to perform specific test:
npm run healthcheck
will perform a healthcheck request of with current setting.npm run basicget
will perform some non-parameter GET request with current setting.npm run connectivity
will perform networking diagnostics of the adatper endpoint.
Connectivity Issues
- You can run the adapter troubleshooting script which will check connectivity, run the healthcheck and run basic get calls.
npm run troubleshoot
- Verify the adapter properties are set up correctly.
Go into the Itential Platform GUI and verify/update the properties
- Verify there is connectivity between the Itential Platform Server and Bluecat Server.
ping the ip address of Bluecat server
try telnet to the ip address port of Bluecat
execute a curl command to the other system
- Verify the credentials provided for Bluecat.
login to Bluecat using the provided credentials
- Verify the API of the call utilized for Bluecat Healthcheck.
Go into the Itential Platform GUI and verify/update the properties
Functional Issues
Adapter logs are located in /var/log/pronghorn
. In older releases of the Itential Platform, there is a pronghorn.log
file which contains logs for all of the Itential Platform. In newer versions, adapters can be configured to log into their own files.