wmantly
24a6a718e0
README.md and docs/architecture.md described authorization as a client-side loop over each of a user's LDAP groups, calling the SSO's GET /api/discovery/resources?group=<cn> once per group. The actual code (utils/access.js, accessibleHosts()) makes a single call to the SSO's GET /api/discovery/access/:uid, which resolves the user's groups server-side and returns the full access projection in one response. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0113gCdnfSCuZr6xvPDxTo3D
Documentation
This directory is the GitHub Pages documentation site for the Jump Host project.
Live site: https://theta42.github.io/jump-host/
Pages
index.md— overview and quick startconnecting.md— usage: the username grammar, the TUI picker, SFTP/WinSCParchitecture.md— how auth, access resolution, key injection, and bridging workinstallation.md— Docker, bare-metal, and theta-env install; the LDAP write-ACL
Local preview
gem install jekyll bundler
cd docs && jekyll serve
# http://localhost:4000/jump-host/
Updating
Edit the markdown, push to master, and GitHub Pages rebuilds automatically.