How to upload file to box.com using box api in appian

Have you tested the box plugin?

It has been released few weeks ago.
community.appian.com/.../box-file-utilities

Jose

Hey Jose,
I gone through this document and the functions as well but I'm unable to get few things like how to get Private Key and Public key for creating JWT via createtoken() function

Upload the Private and Public key files (PEM format) to Appian and pass the document IDs to the createtoken() function. This should be the same key files you used in the Box Developer Console. Either the ones it generated for you, or the ones you generated and uploaded to Box. When you upload the key files to their console, it assigns a kid (Key ID) which is also used in the plugin functions.

Hello Scott,

Thanks for your valuable reply, According to what you have suggest I need to either generate Private Key and Public key or else download it from box and upload it to appian. Then appian will generate unique ID for these documents which I have to use in the place of Public Key and Private Key under createtoken function. Also, It will give me KID from box that I can use in createtoken function as well. Let me know if I'm missing something here or I got it right and its good to go from here?

Also, Can you please tell me how to create .pem file from the downloaded Json file which looks something like below


{
"boxAppSettings": {
"clientID": "",
"clientSecret": "",
"appAuth": {
"publicKeyID": "",
"privateKey": ",
"passphrase": ""
}
},
"enterpriseID": ""
}

That is correct. The Box developer console image shown on page 5 of the "Box File Utilities" PDF illustrates where you either upload your own key files, or have Box generate them for you. It also illustrates the Public Key ID (KID) that Box assigns, though the keys in the image are blurred out for security reasons.

Also in the image on page 5 of the PDF (Box File Utilities) you can see that Box has a link to help in generating your own key files. The link has the text "Learn to generate your own RSA keypair".

The text contained in the "privateKey" part of that JSON can be copied and pasted into a plain text file and named something like privatekey.pem. That text should start with something like "-----BEGIN ENCRYPTED PRIVATE KEY----" and end with "-----END ENCRYPTED PRIVATE KEY-----". Also copy the text for the public key from the console by clicking on the Public Key ID link and paste it into a plain text file and name it something like publickey.pem. Then, upload those files to a knowledge center / folder in Appian. Use the IDs assigned by Appian to the uploaded files when calling the plugin functions.

The text contained in the "privateKey" part of that JSON can be copied and pasted into a plain text file and named something like privatekey.pem. That text should start with something like "-----BEGIN ENCRYPTED PRIVATE KEY----" and end with "-----END ENCRYPTED PRIVATE KEY-----". Also copy the text for the public key from the console by clicking on the Public Key ID link and paste it into a plain text file and name it something like publickey.pem. Then, upload those files to a knowledge center / folder in Appian. Use the IDs assigned by Appian to the uploaded files when calling the plugin functions.

Got it.. Thanks a lot Scott. Your suggestions and guidance is really helpful. Great Work :)

Hey Scott,

I'm able to collect all the information but only one thing i'm struggling here which is related to private key and public key. I have both the files ready but I'm unable to identify where exactly in appian i need to upload them. Is it under admin console>client certificates? or somewhere else? because when I'm trying to upload .pem file under client certificates, Its giving me certificate missing error.