How Can We Help?
Search for answers or browse our knowledge base.
SYNCNOW
SyncNow – connect teams , tools and processes
Connector Security
Connectors data is encrypted in the database, we recommend using TLS for http communication in order not to reveal credentials and other connector data.
Connector Authentication Methods
SyncNow currently supports these authentication methods
- Basic Authentication with username\password
- Basic Authentication with username\token
Webhook Security
Webhooks are used for continuous synchronization and DevOps Gate Processes, SyncNow registers webhooks for you when you activate a Sync process. Webhooks can aurhenticate with SyncNow with the following :
- Anonymous notifications – use this if the source system (Azure DevOps | Jira | ServiceNow etc) supports only anonymous notifications to SyncNow. If Anonymous notifications is checked then SyncNow will not authenticate source requests to its notification API.
We strongly recommend to Add IP restrictions if Anonymous notifications is checked.
- Allowed IP Addresses – check this to allow specific IP addresses or IP ranges in the format of network/mask separated with commas from which SyncNow will allow webhook notifications to its API.
- SyncNow API Key (secret)
Setting SyncNow API Key
The following steps are required to set an API Key for webhook communication:
- Navigate to Users
- Create a user which will be as the user that will be authenticated with SyncNow
- Set an API Key for the user, Click Secret String to Generate a key that will be used for SyncNow authentication
- Save the user information
- Set this user as the authenticating user in webhook security at the system connector security section
