IBM FileNet

configuring an ibm filenet connection (to be updated for filenet) (to be updated for filenet) go to your box developer console https //app box com/developers/console under myapps, click on the ' create new app ' button under 'lets get started' select custom app under 'authentication method' select server authentication (with jwt) and click next name your application e g 'd4iconnector' and click 'create app' click 'view your app' and navigate to the ' configuration ' tab under application scopes select the following options read all files and folders stored in box write all files and folders stored in box manage users (allows app users to be created) note if you want to script out and create app users without docuflow, this setting is not require also this setting can be used for the application to create the app users, and once the process is complete, it can be removed under advanced features select the following options make api calls using the as user header (allows scaling across app users) generate user access tokens under add and manage public keys select 'generate a public/private keypair' and save the json file somewhere secure this json will be required for the box connection configuration this private key cannot be regenerated and must be stored safely and securely under app settings select the 'download json' this json file is required for the box connector after completing these steps go to the 'app authorization' and click 'submit for authorization' return to the admin console, go to 'apps' > custom apps click 'authorize new app' and then enter the client id from the previous step click the authorize button creating a d4i box connection there are two types of connections supported for connecting to box enterprise and appuser when creating a new box connection this can be selected in the 'connection type' dropdown box enterprise connection the enterprise connection uses the default servcice account for connecting to box the following information is required when creating a new enterprise connection enterprise id this can be found in the box admin under the account and billing section client id this can be found in the oauth 2 0 credentials section of the box enterprise application configured earlier client secret this can be found in the oauth 2 0 credentials section of the box enterprise application configured earlier public key id this can be found in the add and manage public keys section of the box enterprise application configured earlier private key this is the private key that corresponds to the public key that was registered with the box enterprise application must be entered properly formatted with multiple lines (not only one long line) passphrase this is the passphrase for the key registered with the box enterprise application box appuser connection the appuser connection uses a defined set of appusers associated with the box enterprise application to conenct to box the d4i box connector will round robin between the provided app users configured in the connector the following information is required when creating a new appuser connection appuser list a list of box app users that have been previously created under the box enterprise application enterprise id this can be found in the box admin under the account and billing section client id this can be found in the oauth 2 0 credentials section of the box enterprise application configured earlier client secret this can be found in the oauth 2 0 credentials section of the box enterprise application configured earlier public key id this can be found in the add and manage public keys section of the box enterprise application configured earlier private key this is the private key that corresponds to the public key that was registered with the box enterprise application must be entered properly formatted with multiple lines (not only one long line) passphrase this is the passphrase for the key registered with the box enterprise application once a connection is created, a connection test can be run to check if the configuration is valid