Production-ready self-hosted password manager release hub, operator wiki, knowledge base and support boundary for PassMan.
|
PassMan public docs is the release hub, operator wiki, knowledge base, support boundary, and trust surface for the self-hosted enterprise vault. Start here: English docs home is the operator entry point. |
PassMan için public release ve dokümantasyon merkezi. Kurulum, operasyon, bilgi bankası, destek paketi ve güvenlik sınırları burada; private kaynak kod ve hassas operasyon verisi bu repoya girmez. Buradan başla: Türkçe operasyon akışı docs/tr; İngilizce ekipler için docs/en. |
Latest Release
|
Docs EN
|
Docs TR
|
KB EN
|
KB TR
|
Security
|
Support
Stable 1.8.22
Windows MSI
TR + EN
Self-hosted
Source private
|
Download release MSI, manifest and support packages. |
Read operator docs Install, verify, operate and recover. |
Check trust boundary Public scope, release trust and secret rules. |
Prepare support evidence Redacted handoff without secrets. |
Sanitized product screenshot. Release binaries stay in GitHub Releases; private source code, signing material and customer data stay out of this repository.
| Contract | How this repository enforces it |
|---|---|
 Customer-safe public surface |
Only docs, sanitized screenshots, release links, knowledge-base articles and public policies live here. |
 Release assets outside git |
MSI files, ZIP packages, manifests and support scripts are delivered through GitHub Releases or the Chrome Web Store. |
 Operator-first navigation |
Quickstart, runbooks, update checks, extension flows, AD agent setup and support evidence paths are linked from the first screen. |
| TR/EN parity |
Turkish and English operator docs are kept as paired routes and validated before publication. |
 Evidence without secrets |
Support handoff asks for redacted context and blocks plaintext credentials, keys, databases, backups and customer data. |
| Signal | Trust signal | Public proof |
|---|---|---|
|
Release assets stay out of git | MSI, release fallback ZIPs, manifest and agent script are linked from GitHub Releases only; browser extension installs use Chrome Web Store. |
 |
Update flow is manifest-led | PassMan verifies the signed manifest, release metadata, SHA-256 checksum and MSI signer before update execution. |
 |
Source boundary is explicit | This public repository contains docs, sanitized screenshots and release links; private product code and signing material are not published here. |
|
Operator evidence is safe by default | Support paths ask for redacted evidence packs and forbid plaintext secrets, private keys, database files and customer data. |
|
TR/EN docs stay paired | Validation checks paired Turkish and English docs plus local links before publication. |
Use this repository as the front desk for the supported PassMan application. It should answer the first operational question without exposing source code, secrets, signing material or customer data.
| I need to... | Open this | Outcome |
|---|---|---|
| Take the shortest safe path from download to first healthy vault | EN admin quickstart / TR hızlı başlangıç | Day-0 install, owner, license, HTTPS, 2FA and backup are sequenced. |
| Run PassMan after go-live | EN operator runbook / TR operasyon runbook | Daily, weekly, monthly and incident routines are clear. |
| Install PassMan on Windows Server | EN install / TR kurulum | MSI installed, service running, first URL verified. |
| Create the first owner and apply license | EN first run / TR ilk kurulum | Owner profile, license state and first vault path are clear. |
| Configure public host and HTTPS | EN HTTPS / TR HTTPS | Required certificate package and browser validation are understood. |
| Fix an operational issue | EN knowledge base / TR bilgi bankası | Safe evidence and diagnosis path are available. |
| Update PassMan or verify release assets | EN release asset verification / TR asset doğrulama | Manifest, checksum, MSI signer and component notes are verified. |
| Pair or troubleshoot the browser extension | EN extension / TR eklenti | Badge count, autofill, save/update login and device pairing behavior are clear. |
| Review browser extension privacy handling | Privacy policy | Chrome/Edge extension data categories, limited-use disclosure and remote-code boundary are documented. |
| Sync Active Directory | EN DC Agent / TR DC Agent | Service install, repair, logs and OU tree sync are documented. |
| Open or diagnose external shares | EN sharing / TR paylasim | Selected records, files, expiry, max opens and offline decrypter flow are clear. |
| Prepare a clean support handoff | EN support evidence pack / TR destek kanıt paketi | Operators know exactly what to collect and what never to send. |
| Role | Primary path | Decision point |
|---|---|---|
| Server administrator | Quickstart, installation, public host and HTTPS | Is the Windows service reachable, signed and backed up? |
| Security owner | Security model, audit posture, release verification | Are secrets encrypted before storage and are updates trusted by manifest plus hash? |
| Support engineer | Support evidence pack, troubleshooting, KB | Can the issue be reproduced with redacted evidence only? |
| Identity operator | DC Agent, extension, operator runbook | Are AD sync, browser pairing and user scope healthy? |
| Turkish operator | TR hızlı başlangıç, TR runbook, TR bilgi bankası | Aynı operasyon yolu Türkçe doküman setinde izlenir. |
This is the public GitHub home for PassMan Enterprise Vault Console. PassMan is now treated as a stable self-hosted Windows Server application, not an alpha or proof build. This repository contains customer-safe documentation, how-to guides, knowledge-base articles, sanitized product screenshots, release notes and links to GitHub Release assets.
This repository does not contain private source code, internal signing material, customer data, databases, backups, certificates or release binaries committed into git.
- Download the latest MSI from GitHub Releases.
- Install it as Administrator on the approved Windows host.
- Open
https://<SERVER_HOST>:1903to verify the service responds. If no trusted certificate is configured yet, expect a managed self-signed certificate warning until the operator installs a PFX/P12 package. - Apply the license and confirm the public host plus HTTPS settings.
- Enable 2FA, confirm audit-chain health and review the overview action queue.
- Install the Chrome Web Store extension, then pair approved browsers.
- Configure PassMan DC Agent Service if AD scope is needed.
- Review backup, restore, update and support-evidence procedures.
| Type | Asset | Purpose | Delivery |
|---|---|---|---|
 |
PassMan-1.8.22-x64.msi | Installs or upgrades PassMan Server on Windows. | GitHub Release |
|
passman-update.json | Signed update manifest verified by PassMan. | GitHub Release |
 |
Chrome Web Store listing | Primary browser extension install and update channel. | Chrome Web Store |
|
passman-chromium-extension.zip | Release archive and development fallback only. | GitHub Release |
 |
passman-share-decrypter.zip | Offline external-share opening tool. | GitHub Release |
 |
passman-ad-agent.ps1 | PassMan DC Agent Service installer and repair script. | GitHub Release |
PassMan-managed updates verify the signed manifest, release asset metadata, SHA-256 checksum and MSI signer thumbprint before starting the MSI flow. A global CA chain is not required for PassMan-managed update trust when the signed manifest pins the local release signer thumbprint. CA-backed or trusted-signing certificates remain recommended for Windows reputation and broad OS-level trust.
| Component | Version | Update path |
|---|---|---|
| PassMan Enterprise Vault Console | 1.8.22 | Windows MSI / Update Center |
| Chromium Browser Extension | 1.3.1 | Chrome Web Store |
| Offline Share Decrypter | 1.2.0 | Bundled support component and release ZIP |
| PassMan DC Agent Service | 1.2.10 | Bundled support component and release script |
| Incident | English | Turkish |
|---|---|---|
| MSI installation fails | EN | TR |
| Update stays around 76 percent | EN | TR |
| DC Agent service cannot connect | EN | TR |
| Extension pairing remains pending | EN | TR |
| Certificate warning | EN | TR |
| Audit chain is partial | EN | TR |
| License is read-only | EN | TR |
| External share package fails | EN | TR |
| Login creates 401 or 403 noise after unlock | EN | TR |
All screenshots are captured from the actual PassMan application with sanitized demo data.
Core console surfaces
| Surface | Screenshot |
|---|---|
| Login / lock screen |  |
| Security posture overview | |
| Password record list |  |
| Sharing package flow |  |
Operations and support surfaces
| Surface | Screenshot |
|---|---|
| Update Center |  |
| Browser extension management |  |
| Active Directory sync tree |  |
| Offline share decrypter |  |
Never upload or paste these materials into this repository, public issues, comments or support threads:
- Plaintext secrets, passwords, share passphrases or vault contents.
- AD bind passwords, agent tokens, license private keys or update signing private keys.
- Databases, backups, PFX/P12 files, private keys or logs with sensitive values.
- Screenshots showing real secret records, users, customer URLs or internal infrastructure.
Use placeholders such as <PASSMAN_URL>, <SERVER_HOST>, <AGENT_ID>, <AGENT_TOKEN> and <LICENSE_CODE> in public examples.
Run before publishing public documentation changes:
npm run validateThe validation checks local links, TR/EN doc parity, required visual assets, real screenshots, stale release wording, forbidden public-site leftovers, large release binaries, secret-like public patterns and encoding artifacts.