--- title: "How do I download provider hosts, drivers and certificates?" slug: "how-do-i-download-provider-hosts-drivers-and-certificates" updated: 2026-10-25T20:37:23Z published: 2026-10-25T20:37:23Z canonical: "support.lusid.com/how-do-i-download-provider-hosts-drivers-and-certificates" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.lusid.com/llms.txt > Use this file to discover all available pages before exploring further. # How do I download provider hosts, drivers and certificates? Some data lives where FINBOURNE's cloud can't reach it: a file share in your office, a database behind your firewall, a spreadsheet tool on your desktop. Luminesce reaches it through provider hosts and drivers you run yourself, and LumiCode can download them, install the ones that are .NET tools, and fetch the client certificate a provider host needs to connect to your domain, all from one prompt. ## Prerequisites - LumiCode installed and signed in. See [How do I install LumiCode?](/v1/docs/how-do-i-install-lumicode) - A licence and entitlements for each binary you want. LumiCode can list a binary that you can't download. - To install a .NET tool from LumiCode, the .NET SDK on your computer. Type `dotnet --version` in a terminal to check. ## Methods ### Method 1: Download a binary 1. Type `/binaries` and press Enter. 2. Choose the binary. See [Appendix: The binaries](/docs/how-do-i-download-provider-hosts-drivers-and-certificates#appendix-the-binaries). 3. Choose the version. The latest is selected. 4. Browse to the folder to download it to, and choose **✔ use this folder**. 5. For a .NET tool, LumiCode asks **Install it now?** Choose yes to install it with `dotnet tool install`, or no to see the command to run later. Either way, LumiCode tells you the command that starts the tool, which is not always the same as its name. Anything that isn't a .NET tool, such as an `.msi` installer or a `.jar` file, is downloaded only. Install it the way that binary documents. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-BFEJEC4H.png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A31%3A20Z&se=2026-10-26T10%3A31%3A20Z&sr=c&sp=r&sig=T8g8F5aKBhvrMnG93mK3EdO3UFyA%2BlkvBo8INddeL30%3D) Updating LumiCode itself LumiCode appears in the list too, with your version marked **(yours)** and any newer one **(newer)**. `/update` is the quicker way to update it, and `/whats-new` shows what a newer version brings first. ### Method 2: Download a client certificate A provider host running outside FINBOURNE's cloud uses a client certificate to authenticate to your domain. It needs both halves: the public certificate and the private key. 1. Type `/certificates` and press Enter. LumiCode lists your certificates, each with its validity dates and whether it's **valid**, **expired** or **revoked**. 2. Choose **download public pem**. 3. Browse to a folder and name the file. LumiCode suggests `client_cert.pem`. Replacing an existing file asks first. 4. Type `/certificates` again and choose **download private pem**. LumiCode suggests `client_key.pem`. On macOS and Linux, LumiCode makes the private key readable only by you. Keep the private key private Anyone with the private key can connect to your domain as you. Store it only on the machine that runs the provider host, and don't email it or put it in a shared folder. **mint (dry run)** shows what creating a certificate would do, and changes nothing. ## Troubleshooting ### The download fails The download service isn't held to the same availability as the rest of the platform. If it looks like an outage, try again later. If a binary is refused, check that you have its licence and entitlements. ### Installing says the tool is already installed `dotnet tool install` doesn't overwrite a tool that's already there. LumiCode shows the `dotnet tool update` command to run instead. ### No certificates are listed LumiCode shows **No client certificates exist for this user/domain yet.** LumiCode doesn't create certificates. See [Managing certificates for Luminesce providers](/v1/docs/managing-certificates-for-luminesce-providers) for how to create and manage certificates. ## Appendix: The binaries | Binary | What it is | Installs as | | --- | --- | --- | | `LumiCode` | LumiCode itself | .NET tool | | `CommandLineTool` | The Luminesce CLI (deprecated for most purposes, use LumiCode instead) | .NET tool | | `LocalFileSystem_Providers` | Providers for local and network (NAS) file systems | .NET tool | | `Email_Providers` | Email providers, for example for a mail server behind an IP restriction | .NET tool | | `Python_Providers` | The C# part of Python providers (not generally for standalone downloads, but required by lumipy to run providers) | .NET tool | | `AwsS3_Providers`, `Azure_Providers`, `Gcs_Providers` | Cloud storage providers, for example for storage behind an IP restriction | .NET tool | | `SqlDb_Providers_…` | `Sql.Db` providers for a database: DB2 on Linux, MySQL, Oracle, PostgreSQL, Snowflake, SQL Server, Sybase ASE, SQLite, DuckDB, AWS DynamoDB, and some combinations of these. Useful for non-internet accessible databases, local databases, etc. | .NET tool | | `Jdbc_Driver` | A generic JDBC driver | `.jar` file | | `PowerBi_Connector` | The Power BI connector | `.msi` installer | | `Odbc_Win64_Driver` | The ODBC driver for 64-bit Windows | `.msi` installer | ## Related articles - [How do I install LumiCode?](/v1/docs/how-do-i-install-lumicode) - [How do I work with Drive and the Configuration Store?](/v1/docs/how-do-i-work-with-drive-and-the-configuration-store)