Skip to content

Remove ssl-root-cas dependency and hardcoded self-signed certificate #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gholliday wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove ssl-root-cas dependency and hardcoded self-signed certificate #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions ParallelBuilds.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,3 +118,28 @@ If the hash doesn't have a key for the run being processed then the bug is assig
* Authentication types
* Username and Password for the Basic and NTLM authentication types.

## SSL Certificate Configuration

This extension uses Node.js's default SSL certificate validation, which should work with most properly configured TFS/Azure DevOps instances. However, if you're running in an enterprise environment with custom Certificate Authorities, you have several options:

### Option 1: Use OS Certificate Store (Recommended)
The best approach is to install your custom root CA certificates in the operating system's certificate store. Node.js will automatically trust certificates from the OS store on:
- **Windows**: Install certificates in the Windows Certificate Store (Local Machine → Trusted Root Certification Authorities)
- **Linux**: Add certificates to the system CA bundle (typically `/etc/ssl/certs/` or `/usr/local/share/ca-certificates/`)
- **macOS**: Install certificates in the Keychain Access (System keychain)

### Option 2: Node.js Environment Variable
If you cannot modify the OS certificate store, you can use Node.js's `NODE_EXTRA_CA_CERTS` environment variable:

```bash
# Set the environment variable to point to your CA certificate file
NODE_EXTRA_CA_CERTS=/path/to/your/custom-root-ca.pem

# Or on Windows
set NODE_EXTRA_CA_CERTS=C:\path\to\your\custom-root-ca.pem
```

This variable should point to a PEM-formatted file containing your custom root CA certificate(s). Multiple certificates can be concatenated in a single file.

**Note**: The environment variable must be set before the Node.js process starts, so it should be configured at the build agent level, not within the build pipeline itself.

Loading