[PR #7] [MERGED] authentication.md: add "path to CA cert" to `verify_ssl` options #6

New issue

Closed

opened 2026-02-27 15:44:45 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 15:44:45 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/proxmoxer/docs/pull/7
Author: @RussellAult
Created: 7/22/2025
Status: ✅ Merged
Merged: 7/26/2025
Merged by: @jhollowe

Base: main ← Head: verify_ssl

📝 Commits (1)

b5fce02 authentication.md: added "path to CA cert" to verify_ssl

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 docs/authentication.md (+2 -2)

📄 Description

In addition to the usual boolean options, the requests module's verify parameter will also accept a string which is the path to a CA certificate file. Currently, the value for proxmoxer's verify_ssl parameter is simply passed verbatim to requests' verify parameter, which means that verify_ssl will also accept a path to a CA cert in addition to a boolean value. This is particularly useful because requests uses its own root CA store rather than relying on the system's, so adding third-party CA certs (e.g. PVE's root CA certificate) can be tricky otherwise.

This PR updates authentication.md to reflect this extended usage of verify_ssl.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/proxmoxer/docs/pull/7 **Author:** [@RussellAult](https://github.com/RussellAult) **Created:** 7/22/2025 **Status:** ✅ Merged **Merged:** 7/26/2025 **Merged by:** [@jhollowe](https://github.com/jhollowe) **Base:** `main` ← **Head:** `verify_ssl` --- ### 📝 Commits (1) - [`b5fce02`](https://github.com/proxmoxer/docs/commit/b5fce02bc93eba6ca1df75c565f282c632113285) authentication.md: added "path to CA cert" to verify_ssl ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/authentication.md` (+2 -2) </details> ### 📄 Description In addition to the usual boolean options, the `requests` module's `verify` parameter will also accept a string which is the path to a CA certificate file. Currently, the value for `proxmoxer`'s `verify_ssl` parameter is simply passed verbatim to `requests`' `verify` parameter, which means that `verify_ssl` will *also* accept a path to a CA cert in addition to a boolean value. This is particularly useful because `requests` uses its own root CA store rather than relying on the system's, so adding third-party CA certs [(e.g. PVE's root CA certificate)](https://pve.proxmox.com/wiki/Import_certificate_in_browser) can be tricky otherwise. This PR updates `authentication.md` to reflect this extended usage of `verify_ssl`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>