Mimecast

introduction this guide tells you how to authenticate the mimecast security connector in swimlane you can authenticate using one of the following methods oauth 2 0 client credentials hmac authentication you will identify the correct mimecast base url for your region, collect the required credentials, and configure the connector in swimlane prerequisites mimecast access requirements you must have mimecast permissions to create or access api credentials used for oauth 2 0 or hmac authentication confirm your mimecast region and base url provide admin access or required permissions to your mimecast account or credentials wherever applicable to make the connector actions working required credentials during setup, you will collect the following based on your authentication method authentication method required credentials notes oauth 2 0 client credentials url, client id, client secret oauth 2 0 client credentials authentication hmac authentication url, access key, app id, app key, secret key hmac authentication mimecast base url you will need to use a mimecast base url use the following table to identify the correct api endpoint for your region api mimecast com is required and is used for initial account discovery region api endpoint check for update urls australia au api mimecast com https //updates au mimecast com/update/descriptors/mfo/latest europe (excluding germany) eu api mimecast com https //updates uk mimecast com/update/descriptors/mfo/latest germany de api mimecast com https //updates de mimecast com/update/descriptors/mfo/latest offshore jer api mimecast com https //updates jer mimecast com/update/descriptors/mfo/latest required api mimecast com n/a used for initial account discovery south africa za api mimecast com https //updates za mimecast com/update/descriptors/mfo/latest united states us api mimecast com https //updates us mimecast com/update/descriptors/mfo/latest oauth 2 0 client credentials this guide uses oauth 2 0 client credentials to authenticate api requests required credentials collect the following values from mimecast client id client secret url (mimecast base url for your region) hmac authentication this authentication method allows you to authenticate using hmac credentials required credentials collect the following values from mimecast access key app id app key secret key url (mimecast base url for your region) access and secret expiration to set access/secrets to never expire you must update the authentication cache ttl setting in the service user's effective authentication profile to never expire 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 mimecast security from the asset type list configuration mimecast hmac authenticates using hmac fill in the asset settings and asset input as shown field description required/optional url a url to the target host required access key access key required app id app id required app key app key required secret key secret key required verify ssl verify ssl certificate optional http proxy a proxy to route requests through optional fields with marks are required configuration mimecast oauth 2 0 client credentials authenticates using oauth 2 0 client credentials fill in the asset settings and asset input as shown field description required/optional url a url to the target host required client id the client id required client secret the client secret required verify ssl verify ssl certificate optional http proxy a proxy to route requests through optional fields with marks are required click create action api permissions you need different permissions for each of the actions to run please refer to the https //integrations mimecast com/documentation/endpoint reference/policies/address alteration/update policy/ to know more troubleshooting if you encounter an authentication error verify url matches your region base url verify credentials are correct and active verify account has admin access or required permissions if using hmac, verify access key, app id, app key, and secret key are from same set of credentials if required, configure http proxy and verify outbound connectivity you have successfully authenticated the mimecast security connector in swimlane