@itentialopensource/adapter-tcpwave/AUTH.md

This adapter integrates with system described as: tcpwaveRestapiStore.

## Authenticating TCPWave Adapter 

This document will go through the steps for authenticating the TCPWave adapter with Personal Access Token Authentication. Properly configuring the properties for an adapter in Itential Platform is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>. 

Companies periodically change authentication methods to provide better security. As this happens this section should be updated and contributed/merge back into the adapter repository.

### Personal Access Token Authentication
The TCPWave adapter requires Personal Access Token Authentication. This means you need to generate a Session Token (valid for 60 days) on the TCPWave server which will enable Itential to make API calls to it.

STEPS  
1. Ensure you have access to a TCPWave server and that it is running
2. Follow the steps in the README.md to import the adapter into Itential Platform if you have not already done so
3. Use the properties below for the ```properties.authentication``` field
```json
"authentication": {
  "auth_method": "static_token",
  "token": "token",
  "token_timeout": -1,
  "token_cache": "local",
  "invalid_token_error": 401,
  "auth_field": "header.headers.TIMS-Session-Token",
  "auth_field_format": "{token}",
}
```
you can leave all of the other properties in the authentication section, they will not be used for TPCWave Authentication.

4. 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, or token.
- Turn on debug level logs for the adapter in Itential Platform Admin Essentials.
- Turn on auth_logging for the adapter in Itential Platform 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.