Box Platform

This is for testing purpose 2.

This is for testing purpose.

https://www.linkedin.com/posts/box_the-box-mcp-server-is-now-in-the-github-mcp-activity-7389044785325600768-GD3F/I just configured this and it is spectacular. All of our knowledge and best practices in one place. My team can simply use the ai_qa_hub tool to ask a question about our style and best practices. We have some specific SQL conventions we use and I had Github Copilot / Box MCP update the file. It came back with the specifics we needed. Exactly what I was looking for.I know other dev platforms allow you to put knowledge in their systems, but we have all of our other corporate knowledge in Box so this just keeps everything consistent and easy to reference.

Thanks to ​ Kamil, and  ​@shurrey Box for yesterday’s overview and demo of Box MCP server.  Recording clipsFull recording hereOverview of MCP Server and Box MCP Server. Recording clip hereOpen Source MCP Server, and customer Q&A. Recording clip here Addressing Challenges of AI in Enterprise DataKamil opened by identifying a pain point for enterprises: the

test post for salesforce integration testing here

Hi, I’d like to make a request to have the dll in Nuget package signed by Box. The package itself is signed, but Box.V2.dll. Microsoft is introducing Smart App Control and having dlls signed gets more important.

I’d like to apply a metadata template from another enterprise (let’s call it Enterprise B) to files from my enterprise (Enterprise A). When I attempt to do so via the Box API, I receive 403 Forbidden. I’ve tried a number of variations, to get an idea of what responses I can expect: If Enterprise B doesn’t exist - 400 Bad Request, Invalid metadata scope. If Enterprise B does exist but the metadata template does not - 404 Not Found, Specified Metadata Template not found. If Enterprise B does exist and the metadata template does exist - 403 Forbidden. I suspect that the user making the call needs permissions that they don’t have, but it’s not clear to me what permissions that user needs - there don’t appear to be any permissions specific to metadata. What must I do to allow a user from Enterprise A to apply a metadata template from Enterprise B to files in Enterprise A?

Our app is currently under review. Even though it is in the review process, is it okay for our customers to use it? Are there any restrictions, such as a maximum number of connections?

I am using trial version of Enterprise Box and I have created Box Custom application (authorized by Box admin). Then I generated a private key PK for that Box application and I use this PK to connect to Box App from AWS Kendra. I use Kendra Developer Edition in this test. This method used to work, however today I received the below connection error after providing new PK to Kendra. PK is passed to Kendra using Secrets Manager. Error connecting to customer repository: Error parsing PKCS private key for Box Developer Edition. I made sure the PK is copied properly to Kendra. I also tested connectivity using the same PK and Box SDK and I can connect successfully to Box App programmatically using Python, however the connection from AWS Console fails. What can cause this error? This is private key format generated from BOX Application. It contains “\n” character as text. I normally copy “privateKey” into secret in Secrets Manager Kendra

Dear Forum, When running BoxAPI through an internal proxy, I am having trouble because [EE certificate key too weak] SSLError has occurred. Internal proxy information is set in Python-BoxSDK, Skipping certificate validation will prevent SSLError from occurring. Please let me know the cause of the above problem and how to resolve it. My personal opinion is that the security strength of the certificate sent from the internal proxy is too weak. 【SSL Error】 requests.exceptions.SSLError: HTTPSConnectionPool(host=‘api.box.com’, port=443): Max retries exceeded with url: /oauth2/token (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:997)’)))

I have an intermittent problem where the Python Box SDK is raising the following exception when generating a down scoped token. The code works most of the time but occasionally will stop working for a few minutes. Do the JWT tokens need to be expired or released? The code is being run from an AWS Lambda and the downscoped token only needs to be used once. Is there API rate limit. I don’t think I’m near it usage would be less then 30 an hour but maybe multiple in quick succession. Our Box Account is Business Plus. boxsdk.exception.BoxAPIException: Message: The subject_token provided is invalid The code that is generating the error is in the used to create a downscoped token that can be used by a Box Preview embed: config = JWTAuth.from_settings_file('cert/abcd_1234_config.json') client = Client(config) target_file = client.file(file_id=file_id) token_info = client.downscope_token(['item_preview

Hello there I am developing an integration for a customer that uses BOX. I have created my own box account to develop and test the integration. Today i wanted to test it out on the customers enterprise. They could add and authorize the app easily via the client id. However the app service account needs to be added as a collaborator to the folder it needs to see. This is where we ran into trouble, as BOX refused to add the service account since it was from a different enterprise. Is it possible to add a serviceaccount from a different enterprise at all? I am going at this the wrong way or is there some trick that i have missed. Best regards Malte

Hi, I’m a little stuck on this. We use box for our storage for clients (organisations) and with each client, we open a new folder. The functionality I’m looking for is for an internal admin webapp. When a user logs in to the admin app, I want to retrieve a service account token so then when they create an organisation, it triggers a new folder created in the enterprise account. All the client_ids etc are in the .env and in the dev console, the custom app is fine. Here is a copy of my server.js: const BoxSDK = require('box-node-sdk'); // Box configuration app.get('/api/box-access-token', cors(corsOptions), async (req, res) => { const sdkConfig = { boxAppSettings: { clientID: process.env.BOX_CLIENT_ID, clientSecret: process.env.BOX_CLIENT_SECRET, }, enterpriseID: process.env.ENTERPRISE_ID, } const sdk = BoxSDK.getPreconfiguredInstance(sdkConfig) const client = sdk.getAnonymousClient()