Recorded Future Sandbox

introduction this guide tells you how to authenticate the recorded future sandbox connector in swimlane using http bearer token authentication oauth 2 0 client credentials you will generate an api token or oauth client credentials in recorded future, collect the required identifiers, and configure the connector in swimlane prerequisites recorded future access requirements you must have recorded future permissions to access the recorded future platform generate api tokens create oauth clients (if applicable) access api services required credentials during setup, you will collect api base url api token (bearer token) client id (oauth) client secret (oauth) token url (oauth) authentication methods overview the recorded future sandbox connector supports http bearer token authentication oauth 2 0 client credentials recorded future setup take the following steps to generate an api token (bearer authentication) log in to the recorded future platform click your profile icon (top right corner) select settings navigate to api access click generate new token enter a name for the token click generate copy and securely store the token this token will not be shown again store it securely take the following steps to configure oauth client credentials (if applicable) log in to the recorded future platform navigate to api / integrations settings create a new oauth application/client select client credentials as the grant type assign required permissions/scopes save the application copy client id client secret token url connector configuration in swimlane log in to turbine from the left hand navigation pane, click orchestration → assets click the plus icon select recorded future sandbox from the asset type list configuration – http bearer authentication field description required url recorded future sandbox api base url yes token api token (bearer token) yes verify ssl enable or disable ssl verification no http proxy proxy configuration no configuration – oauth 2 0 client credentials field description required url recorded future sandbox api base url yes token url oauth token endpoint yes client id oauth client id yes client secret oauth client secret yes verify ssl enable or disable ssl verification no http proxy proxy configuration no troubleshooting authentication failures may occur due to invalid api token or oauth credentials incorrect api base url missing permissions or scopes expired or revoked token fix regenerate api token if needed verify credentials in recorded future ensure correct api endpoint confirm permissions and access level you have successfully authenticated the recorded future sandbox connector in swimlane sources recorded future api documentation https //api recordedfuture com/ https //api recordedfuture com/ recorded future support https //support recordedfuture com/ https //api recordedfuture com/