Netskope Security V1 and V2 SE

introduction this guide tells you how to authenticate the netskope security v1 and netskope security v2 connectors in swimlane using api token authentication you will generate the required api token in netskope, collect the required identifiers, and configure the connector in swimlane prerequisites netskope access requirements you must have netskope administrative permissions to access the netskope tenant generate rest api tokens view rest api v1 and rest api v2 settings assign or inherit the permissions required for the api endpoints you intend to use required credentials during setup, you will collect netskope tenant url netskope v1 api token netskope v2 api token authentication methods overview the netskope connectors support the following authentication methods netskope security v1 – token authentication using the token field netskope security v2 – api key authentication using the netskope api token header netskope setup take the following steps to generate a netskope v1 api token log in to your netskope tenant navigate to settings > tools > rest api v1 ensure rest api v1 access is enabled if required by your tenant configuration generate or copy the existing rest api v1 token store the v1 token securely for use in swimlane take the following steps to generate a netskope v2 api token log in to your netskope tenant if your tenant uses rbac v3, navigate to settings > administration > administrators & roles create or select a role with the permissions required for the rest api v2 endpoints you plan to use go to administrators and click service account create a service account and assign the role create the token and copy it when prompted if your tenant uses the rest api v2 token page instead, navigate to settings > tools > rest api v2 click new token, select the required endpoints or permissions, then click save copy the generated v2 token and store it securely take the following steps to identify the netskope tenant url log in to your netskope tenant copy the tenant hostname from the browser address bar use that tenant hostname as the base url in swimlane connector configuration in swimlane log in to turbine from the left hand navigation pane, click orchestration and click assets click the plus icon to open the configure your connector asset window select the netskope connector version you want to configure fill in the asset settings and asset input as shown below configuration – netskope security v1 field description required/optional url netskope tenant url required token netskope rest api v1 token required configuration – netskope security v2 field description required/optional url netskope tenant url required netskope api token netskope rest api v2 token required verify ssl enable or disable ssl verification optional http proxy optional proxy configuration optional troubleshooting if authentication fails ensure you are using the correct token for the correct connector version verify the tenant url is correct and reachable from swimlane confirm the token has not expired or been revoked for v2, ensure the token includes permissions for the endpoints you intend to use if your tenant uses rbac v3, verify the assigned role includes the necessary api permissions check proxy and ssl settings if requests are blocked or fail to connect you have successfully authenticated the netskope security v1 and netskope security v2 connectors in swimlane sources netskope api tokens documentation https //docs netskope com/en/api tokens 2/ https //docs netskope com/en/api tokens 2/ netskope rest api v1 overview https //docs netskope com/en/rest api v1 overview/ https //docs netskope com/en/rest api v1 overview/ netskope rest api v2 overview https //docs netskope com/en/rest api v2 overview 312207/ https //docs netskope com/en/rest api v2 overview 312207/