Cofense Triage

introduction this guide tells you how to authenticate the cofense triage connector in swimlane using oauth 2 0 client credentials you will generate api credentials in cofense triage, collect required identifiers, and configure the connector in swimlane prerequisites cofense triage access requirements you must have access to cofense triage platform (with administrative privileges) api access enabled for your account permission to generate api tokens and oauth credentials required credentials during setup, you will collect url (cofense triage api endpoint) client id client secret api token (generated in cofense triage) cofense triage setup take the following steps to generate an api token log in to the cofense triage platform navigate to administration → account management → operators locate the superuser account that will be used for api access in the api token actions column, click the (+) icon copy the generated api token and store it securely this token will be used along with your account credentials for authentication take the following steps to obtain oauth credentials ensure your application is registered with cofense triage retrieve the following from your cofense environment client id client secret confirm api access is enabled for your account api endpoint format the general cofense triage api url format is https //\<hostname>/api/public/v2/ example https //your instance/api/public/v2/reports connector configuration in swimlane log in to turbine from the left hand navigation pane, click orchestration and click assets asset homepage opens click the plus icon to open the configure your connector asset window select cofense triage from the asset type list fill in the asset settings and asset input as shown configuration oauth 2 0 client credentials field description required/optional url cofense triage api base url required client id client id from cofense required client secret client secret from cofense required verify ssl enable/disable ssl verification optional http proxy optional proxy configuration optional fields with marks are required troubleshooting if authentication fails ensure the api token is valid and active verify client id and client secret are correct confirm the api base url is correct ensure your account has api access permissions check for network/proxy restrictions verify ssl settings if connection issues occur you have successfully authenticated the cofense triage connector in swimlane sources cofense triage api documentation https //community cofense com https //community cofense com