# OpenVPN
OpenVPN is an open-source VPN protocol and commercial networking platform; it matters here as a secure-connectivity and tenant-administration layer.
## Historical and Technical Context
This page lays out a prospective **remote-access and federated-identity stack**. NoMachine provides remote desktop access; OpenVPN CloudConnexa supports SAML SSO through external identity providers, including OneLogin; and UTM virtualizes or emulates operating systems on Apple devices. [S25][S26][S31] The personalized subdomains suggest configuration planning or tenant discovery, but they are not themselves proof that the tenants existed or were active. iOSGods sits outside the enterprise identity stack and likely belongs to the adjacent investigation of alternate iOS distribution.
## Role in Scanned_20260730-1802
The primary identifying evidence appears on PDF page 12. A lined page with a small blue tab or sticky fragment at the top bearing partial text. The body is a compact stack of domains and identity/network acronyms. Several entries are indented to show tenant-specific subdomains. Within that page, OpenVPN helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure.
## Notebook Evidence
- `Scanned_20260730-1802.pdf`, PDF page 12: "openvpn.net"
- `Scanned_20260730-1802.pdf`, PDF page 12: "mcgill.openvpn.net ?"
- `Scanned_20260730-1802.pdf`, PDF page 12: "cloud.openvpn.net (admin portal)"
**Evidentiary status:** Visible evidence: domains and explicit “admin portal.” Verified fact: CloudConnexa supports SAML SSO with identity providers. Strong inference: the author was mapping how remote machines, VPN access, virtual machines, and identity federation could be unified.
The canonical name **OpenVPN** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers.
## Relationships
On PDF page 12, OpenVPN appears in the same evidentiary cluster as [[NoMachine|NoMachine]], [[Single Sign-On|Single Sign-On]], [[Security Assertion Markup Language|Security Assertion Markup Language]], [[iOSGods|iOSGods]], [[UTM|UTM]], [[OneLogin|OneLogin]]. These links record page-level proximity and the reconstruction's systems map; they do not by themselves prove corporate ownership or a direct technical dependency.
## Cross-Notebook Significance
Pages 18-23 extend the iOS-distribution branch, while pages 5 and 32-35 extend the enterprise provisioning and fleet branch. The recurring target is **one identity and control layer spanning many devices and environments**.
## Missed Signals and Open Leads
Determine whether the tenant subdomains were hypothetical naming conventions, DNS records, or configured services. Do not attempt authentication. Recover configuration exports, SAML metadata, or administrative correspondence if preserved.
## Sources
- [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF page 12.
- `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`.
- **[S25]** OpenVPN CloudConnexa, “Set SAML Single Sign-On Authentication”. https://openvpn.net/cloud-docs/owner/settings/settings---user-authentication/set-saml-single-sign-on-authentication-for-users.html
- **[S26]** NoMachine, “Enterprise Desktop”. https://www.nomachine.com/enterprise/enterprise-desktop-products/enterprise-desktop
- **[S31]** OpenVPN, “Introduction to CloudConnexa”. https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/introduction-to-cloudconnexa.html
## Scanned_20260730-1659 overlay
**Source evidence:** [[Scanned_20260730-1659#PDF page 25 — Storage Access Framework and open mobile infrastructure map|page 25]], [[Scanned_20260730-1659#PDF page 65 — Cloud-provider and identity architecture dated August 8, 2021|page 65]].
[[Storage Access Framework|SAF]] is Android's user-mediated document/storage access layer. F-Droid, APKPure, and APKMirror are distribution sources with different governance models. [[Android Open Source Project|AOSP]] is the Android base; Ubuntu Touch, PinePhone, and Librem 5 represent alternate mobile OS/hardware paths. Firebase is centralized backend infrastructure; Tor, OpenVPN, and FreedomBox provide privacy, secure transport, and self-hosting.
**Relationship overlay:** [[Android Open Source Project|Android Open Source Project]] · [[APKMirror|APKMirror]] · [[APKPure|APKPure]] · [[Auth0|Auth0]] · [[Box|Box]] · [[Cloud API|Cloud API]] · [[Cloudflare|Cloudflare]] · [[Cloudinary|Cloudinary]] · [[DigitalOcean|DigitalOcean]] · [[F-Droid|F-Droid]] · [[Firebase|Firebase]] · [[FreedomBox|FreedomBox]] · [[GoDaddy|GoDaddy]] · [[Librem 5|Librem 5]] · [[Microsoft Secure Email|Microsoft Secure Email]] · [[PinePhone|PinePhone]].
This evidence supplements rather than replaces earlier notebook interpretations. It connects the existing note to [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Scanned_20260730-1659|Scanned_20260730-1659]].