cs-image-system-posix-identity-plugin 0.1.1__tar.gz

cs_image_system_posix_identity_plugin-0.1.1/.gitignore

@@ -0,0 +1,26 @@
+.envrc
+# Okta API-integration key material -- never commit
+.private_key.pem
+.private_key.json
+.public_key.json
+*.pem
+__pycache__/
+*.py[cod]
+.pytest_cache/
+*.egg-info/
+dist/
+build/
+.venv/
+.DS_Store
+packages/**/*.code-workspace
+trial
+tfmodules/tftest
+YAML_DUMP.yaml
+.obsidian
+.tofu-plugin-cache/
+_uncommitted/
+target/
+# never publishable, whatever the root (stage 35 refuses them; stage 40's publish-tree checks the policy)
+tfplan
+*.tfstate
+*.tfstate.backup

cs_image_system_posix_identity_plugin-0.1.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

cs_image_system_posix_identity_plugin-0.1.1/PKG-INFO

@@ -0,0 +1,225 @@
+Metadata-Version: 2.5
+Name: cs-image-system-posix-identity-plugin
+Version: 0.1.1
+Summary: The posix identity plugin: groups, users, memberships, keys and sudo as POSIX accounts on the machines, with ids the configuration declares; alone, or beside Okta for groups
+Project-URL: Repository, https://github.com/infrastructurebuilder/cs-image-system-3
+Project-URL: Documentation, https://github.com/infrastructurebuilder/cs-image-system-3/blob/develop/docs/OPERATIONS.md
+Project-URL: Package README, https://github.com/infrastructurebuilder/cs-image-system-3/blob/develop/packages/posix-identity-plugin/README.md
+Author-email: Mykel Alvis <mykelalvis@infrastructurebuilder.org>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: cs-image-system-system==0.1.1
+Requires-Dist: pydantic>=2.13
+Description-Content-Type: text/markdown
+
+<!--
+SPDX-FileCopyrightText: 2026 Mykel Alvis <mykelalvis@infrastructurebuilder.org>
+
+SPDX-License-Identifier: Apache-2.0
+-->
+
+# cs-image-system-posix-identity-plugin
+
+The posix identity plugin: groups and users that exist as **POSIX accounts on
+the machines**, with ids the configuration declares. It registers a group
+builder and a user builder, both `type: posix`, under the identity type
+`posix`. Neither has a terraform root or asks a directory: the configuration
+is the authority, and what it describes is written onto the machines.
+
+Why it exists (stage 75): on a machine of an Okta-managed group, OPA's agent
+creates each person's account and user-private group, but **never the group
+that owns the machine** -- `getent group coops` on `coops-model-005` found
+nothing, so the group's `2770` storage subtree was owned by a bare number no
+account belonged to. This plugin makes that group exist, with the right id.
+
+What it does, and when:
+
+- **At the bake of an instance image** owned by a posix group, the group is
+  created with its declared `gid:` -- or adopted when it already stands with
+  that gid, or the bake stops when it stands with another (a name known to
+  two sides with two ids is a configuration error, the operator's rule).
+- **A base image** that declares `identity_types: [posix]` checks that the
+  shadow tools and sudo are there (`groupadd`, `useradd`, `gpasswd`,
+  `visudo`); it installs nothing, since every supported family ships them.
+- **Generated IaC** writes a posix group's gid as the number: there is no
+  identity root to read it from, so the storage and instance roots declare
+  no remote state for it.
+- **`validate`** resolves every POSIX id the configuration claims (see
+  "Configuration reference").
+
+- **After every applying instance run**, each launched, RUNNING machine of
+  a posix group gets the group's accounts script over the runtime's session
+  (SSM on AWS, the guest session on GCE), run as root: every member and
+  admin as an account (its `uid:`, a user-private group of the same name
+  and id, a home, exactly its `public_keys:` as `authorized_keys`), the
+  members (admins among them) as the group's members, and NOPASSWD sudo
+  for the admins unless `admin_sudo: false`. The script is
+  [`accounts.py`](src/cs_image_system/posix_identity_plugin/accounts.py)'s;
+  it is idempotent, adopts what stands equal and refuses what stands
+  different. It runs after launch rather than in the launch script on
+  purpose: the launch script is the machine's immutable snapshot, so a
+  membership change there would mean a new machine; here it means the next
+  applying run. A machine that is off waits for a run that finds it
+  running; a machine that booted this run is waited for (bounded).
+  A failure is logged as an error naming the machine and never stops the
+  run; the next applying run tries again.
+
+## The login proof
+
+`verify login` (CI's perform job runs it) logs into each standing machine
+of a posix group as the group's **proof user** and checks it is in the
+group -- access proved, not only health:
+
+- **The proof user** is a member or admin declared on a posix user
+  builder with `is_service_account: true`, a `uid:` and its public key in
+  `public_keys:` (the first such member by name). A group without one is
+  skipped, naming why.
+- **Its private key** reaches the proof as `CSIS_PROOF_SSH_KEY` (the key
+  itself, or a path to it; in CI a repository secret no gate reads).
+- **ssh never touches the machine's address.** The runtime gives a
+  tunnel (`ssh_proxy_command`): on AWS, Session Manager's
+  `AWS-StartSSHSession` -- the path packer already bakes through, so a
+  private subnet with no public address and no inbound rule is fine, given
+  `ssm:StartSession` on the instance and the document and the
+  session-manager plugin; on GCE, an IAP tunnel. The host key is accepted
+  into a throwaway known-hosts file: the tunnel already chose the machine
+  by its instance id.
+- **The checks**, stopping at the first that fails: the proof key is
+  there; the runtime gives a tunnel; the login succeeds as the proof user;
+  the group is among its groups. The record says `as: proof key`.
+
+## Beside Okta
+
+An `okta-tf` group builder names a posix group builder as its `posix:`
+delegate (required since stage 75; `posix: none` is the explicit way to
+have none). Its groups stay OPA's -- created there, members kept there --
+and the delegate makes them exist on the machines:
+
+- **OPA's agent makes accounts just-in-time**: it creates an account at a
+  login and deletes it later, and `userdel` drops every supplementary
+  group (observed on coops-model-005, stage 75 step 1). A membership
+  written after an apply would not hold, so the delegate installs a
+  **login hook**: an `optional` `pam_exec` session line in
+  `/etc/pam.d/sshd` runs `/usr/local/sbin/csis-group-login`, which adds
+  the logging-in user to every group whose member list
+  (`/etc/csis/groups/<group>.members`) names them. It never fails a login.
+- **The hook is baked** into every instance image of an Okta group whose
+  builder names a delegate, and **installed again by every applying run**
+  (idempotently), so a machine that stands and is never re-baked gets it.
+- **After each applying instance run**, each running machine of such a
+  group gets the group with OPA's gid (the Okta builder asks OPA,
+  read-only), its member list (members and admins, the root group's
+  admins merged as OPA has them), and the members whose accounts stand at
+  that moment joined at once. No account is created: OPA's agent makes
+  those.
+- **`posix_ssh_keys: true`** on the Okta builder also writes each
+  member's declared `public_keys:` to `/etc/csis/keys/<user>`, which the
+  hook installs at login -- a key path beside OPA's certificates, off by
+  default.
+
+## Prerequisites and integration
+
+- **Installed** with the release (it is one of the packages `cs-image-system`
+  pins); its entry point is `cs_image_system.plugins.group`, which registers
+  both builders.
+- **Machines**: any family with the shadow tools and sudo -- AlmaLinux/RHEL
+  (`shadow-utils`, `sudo`) and Debian (`passwd`, `sudo`) do by default. The
+  bake fails at the prerequisite check otherwise, naming nothing more than
+  the missing command.
+- **Base images**: a base whose instance images belong to posix groups must
+  declare `identity_types: [posix]` (or list it beside `okta`); `validate`
+  refuses an image whose group resolves to an identity type its base does
+  not declare.
+- **No credentials, no network, no state.** The builders read the
+  configuration only.
+
+## Configuration reference
+
+A group builder and a user builder, in `cfg/group-builders.yml`:
+
+```yaml
+group_builders:
+  - name: posix-local
+    type: posix
+    shell: /bin/bash        # the login shell of this builder's users (default)
+    admin_sudo: true        # the group's admins get NOPASSWD sudo (default)
+user_builders:
+  - name: posix-users
+    type: posix
+```
+
+| Builder field | Type | Default | Meaning |
+|---|---|---|---|
+| `shell` | str | `/bin/bash` | the login shell given to accounts this plugin creates |
+| `admin_sudo` | bool | `true` | a group's `admins` may run anything as root without a password (their accounts have none: keys only); `false` leaves sudo to the operator |
+
+A group of a posix builder declares its id as `gid:`; a user of a posix user
+builder declares `uid:` and its keys as `public_keys:`:
+
+```yaml
+groups:
+  - name: pxgroup
+    type: posix-local
+    gid: 3101
+    members: [taylor_tango, uma_uniform]
+    admins: [taylor_tango]
+users:
+  - name: taylor_tango
+    type: posix-users
+    first_name: Taylor
+    last_name: Tango
+    uid: 3201
+    public_keys: ["ssh-ed25519 AAAA... taylor@example.invalid"]
+```
+
+The ids, checked at `validate` (the core's `check_posix_ids`, over the
+claims both builders make):
+
+- every posix group declares a `gid:` and every posix user a `uid:`, each at
+  least 1024 (below that are the system's own accounts; the `Group` model
+  refuses a lower gid when it loads, and the check holds uids to the same
+  floor);
+- a user's private group takes the user's name and uid, so a declared group
+  of the same name with another gid is refused, naming both;
+- two groups with one gid, or two users with one uid, are refused;
+- names are POSIX names a machine accepts: lower case, a letter or
+  underscore first, at most 32 characters, `.`, `_` and `-` allowed.
+
+A posix group or user that declares `attributes:` is refused: the ids are
+`gid:` and `uid:`, not provider attributes.
+
+## What it tests and verifies
+
+- **In the bake** (the base image's in-bake checks): the four commands
+  exist; for an instance image, the owning group stands with its gid
+  (`getent group <name>`).
+- **At `validate`**: the id rules above, every one named with the sides
+  that disagree; and every member or admin of a posix group must be a
+  user of a posix user builder with a `uid:` (the accounts the script
+  creates).
+- **Its tests**: [`tests/test_posix_accounts.py`](tests/test_posix_accounts.py)
+  holds the script's parts as text and checks the whole script parses;
+  the system's `tests/test_v2_posix_identity.py` holds the builders, the
+  id resolution and the generated IaC; the container leg of `just
+  full-test` runs the script on AlmaLinux 10 and Debian, twice, against an
+  equal and a differing pre-existing group.
+
+## When it fails
+
+| Symptom | Meaning | Do |
+|---|---|---|
+| `group <g>: no side supplies its id ... declare one (gid:)` at `validate` | a posix group or user without an id | declare `gid:` (group) or `uid:` (user) |
+| `group <g>: the configuration supplies id <a> and the configuration (user-private group) supplies <b>` | a declared group shares its name with a posix user | rename one; a user's private group is the user's name |
+| `groups <a>, <b> all have id <n>` | two names, one id | give each its own |
+| `posix accounts: group <g> has gid <x> here; the configuration says <y>` in a bake's output (exit 3) | the base image already has that group with another gid | change the declared gid, or the base |
+| `posix accounts: gid <n> belongs to group <h> here; the configuration gives it to <g>` (exit 3) | the base image already uses that gid for another group | choose a free gid |
+| `command -v visudo` fails in a base bake | the family lacks sudo | install it in the OS builder's packages |
+| `posix group <g>: <u> has no posix account` at `validate` | a member or admin of a posix group is not a posix user with a uid | declare it on a `type: posix` user builder with a `uid:`, or take it out of the group |
+| `Instance <i>: the accounts script of group <g> FAILED (exit <n>)` in a run's log, with the script's `posix accounts:` lines above it | the machine refused (a group or user standing with another id) or could not be reached | read the lines; fix the id or the machine; the next applying run tries again |
+| `login proof <i>: proof key: FAILED -- CSIS_PROOF_SSH_KEY is not set` | the proof user's private key is not in the environment (CI: the secret is unset) | set the secret, or take `is_service_account` off if no proof is wanted |
+| `login proof <i>: tunnel: FAILED -- the runtime gives no ssh tunnel to <i>` | the machine is not running, or the runtime has no session mechanism | start it, or declare the runtime's `session_mechanism` |
+| `login proof <i>: login: FAILED -- ssh <u>@<i> id: exit 255 ...` | the key was refused, or the tunnel could not open (AWS: `ssm:StartSession` on `AWS-StartSSHSession`, the session-manager plugin). In CI the tail names the role: the proof runs under the WRITE identity since stage 89, and a workflow from before 0.1.1.dev22 made it under the read-only role, which may not open a session | read the tail; check the key pairs with `public_keys:` and the role's grant; in CI, take the release whose workflow makes the proof before the read-only identity is taken back |
+| `login proof <i>: in its group: FAILED` | the account stands but is not in the group | an applying instance run brings membership back; read its accounts log |
+| `Instance <i>: <u> has no account here yet; not a member of <g> until it does` (a warning) | a member's account does not stand yet | nothing: the next run adds it once the account exists |
+| `identity: group '<g>' was managed by the system but is missing from the YAML` at `validate` | a posix group was deleted from the YAML; a group the system once managed never leaves it (DESIGN N19) -- met 2026-10-04 retiring the live proof's group | put the entry back with `unmanaged: true` and no members; its gid stays claimed by the name, and nothing on any machine is touched |

cs_image_system_posix_identity_plugin-0.1.1/README.md

@@ -0,0 +1,210 @@
+<!--
+SPDX-FileCopyrightText: 2026 Mykel Alvis <mykelalvis@infrastructurebuilder.org>
+
+SPDX-License-Identifier: Apache-2.0
+-->
+
+# cs-image-system-posix-identity-plugin
+
+The posix identity plugin: groups and users that exist as **POSIX accounts on
+the machines**, with ids the configuration declares. It registers a group
+builder and a user builder, both `type: posix`, under the identity type
+`posix`. Neither has a terraform root or asks a directory: the configuration
+is the authority, and what it describes is written onto the machines.
+
+Why it exists (stage 75): on a machine of an Okta-managed group, OPA's agent
+creates each person's account and user-private group, but **never the group
+that owns the machine** -- `getent group coops` on `coops-model-005` found
+nothing, so the group's `2770` storage subtree was owned by a bare number no
+account belonged to. This plugin makes that group exist, with the right id.
+
+What it does, and when:
+
+- **At the bake of an instance image** owned by a posix group, the group is
+  created with its declared `gid:` -- or adopted when it already stands with
+  that gid, or the bake stops when it stands with another (a name known to
+  two sides with two ids is a configuration error, the operator's rule).
+- **A base image** that declares `identity_types: [posix]` checks that the
+  shadow tools and sudo are there (`groupadd`, `useradd`, `gpasswd`,
+  `visudo`); it installs nothing, since every supported family ships them.
+- **Generated IaC** writes a posix group's gid as the number: there is no
+  identity root to read it from, so the storage and instance roots declare
+  no remote state for it.
+- **`validate`** resolves every POSIX id the configuration claims (see
+  "Configuration reference").
+
+- **After every applying instance run**, each launched, RUNNING machine of
+  a posix group gets the group's accounts script over the runtime's session
+  (SSM on AWS, the guest session on GCE), run as root: every member and
+  admin as an account (its `uid:`, a user-private group of the same name
+  and id, a home, exactly its `public_keys:` as `authorized_keys`), the
+  members (admins among them) as the group's members, and NOPASSWD sudo
+  for the admins unless `admin_sudo: false`. The script is
+  [`accounts.py`](src/cs_image_system/posix_identity_plugin/accounts.py)'s;
+  it is idempotent, adopts what stands equal and refuses what stands
+  different. It runs after launch rather than in the launch script on
+  purpose: the launch script is the machine's immutable snapshot, so a
+  membership change there would mean a new machine; here it means the next
+  applying run. A machine that is off waits for a run that finds it
+  running; a machine that booted this run is waited for (bounded).
+  A failure is logged as an error naming the machine and never stops the
+  run; the next applying run tries again.
+
+## The login proof
+
+`verify login` (CI's perform job runs it) logs into each standing machine
+of a posix group as the group's **proof user** and checks it is in the
+group -- access proved, not only health:
+
+- **The proof user** is a member or admin declared on a posix user
+  builder with `is_service_account: true`, a `uid:` and its public key in
+  `public_keys:` (the first such member by name). A group without one is
+  skipped, naming why.
+- **Its private key** reaches the proof as `CSIS_PROOF_SSH_KEY` (the key
+  itself, or a path to it; in CI a repository secret no gate reads).
+- **ssh never touches the machine's address.** The runtime gives a
+  tunnel (`ssh_proxy_command`): on AWS, Session Manager's
+  `AWS-StartSSHSession` -- the path packer already bakes through, so a
+  private subnet with no public address and no inbound rule is fine, given
+  `ssm:StartSession` on the instance and the document and the
+  session-manager plugin; on GCE, an IAP tunnel. The host key is accepted
+  into a throwaway known-hosts file: the tunnel already chose the machine
+  by its instance id.
+- **The checks**, stopping at the first that fails: the proof key is
+  there; the runtime gives a tunnel; the login succeeds as the proof user;
+  the group is among its groups. The record says `as: proof key`.
+
+## Beside Okta
+
+An `okta-tf` group builder names a posix group builder as its `posix:`
+delegate (required since stage 75; `posix: none` is the explicit way to
+have none). Its groups stay OPA's -- created there, members kept there --
+and the delegate makes them exist on the machines:
+
+- **OPA's agent makes accounts just-in-time**: it creates an account at a
+  login and deletes it later, and `userdel` drops every supplementary
+  group (observed on coops-model-005, stage 75 step 1). A membership
+  written after an apply would not hold, so the delegate installs a
+  **login hook**: an `optional` `pam_exec` session line in
+  `/etc/pam.d/sshd` runs `/usr/local/sbin/csis-group-login`, which adds
+  the logging-in user to every group whose member list
+  (`/etc/csis/groups/<group>.members`) names them. It never fails a login.
+- **The hook is baked** into every instance image of an Okta group whose
+  builder names a delegate, and **installed again by every applying run**
+  (idempotently), so a machine that stands and is never re-baked gets it.
+- **After each applying instance run**, each running machine of such a
+  group gets the group with OPA's gid (the Okta builder asks OPA,
+  read-only), its member list (members and admins, the root group's
+  admins merged as OPA has them), and the members whose accounts stand at
+  that moment joined at once. No account is created: OPA's agent makes
+  those.
+- **`posix_ssh_keys: true`** on the Okta builder also writes each
+  member's declared `public_keys:` to `/etc/csis/keys/<user>`, which the
+  hook installs at login -- a key path beside OPA's certificates, off by
+  default.
+
+## Prerequisites and integration
+
+- **Installed** with the release (it is one of the packages `cs-image-system`
+  pins); its entry point is `cs_image_system.plugins.group`, which registers
+  both builders.
+- **Machines**: any family with the shadow tools and sudo -- AlmaLinux/RHEL
+  (`shadow-utils`, `sudo`) and Debian (`passwd`, `sudo`) do by default. The
+  bake fails at the prerequisite check otherwise, naming nothing more than
+  the missing command.
+- **Base images**: a base whose instance images belong to posix groups must
+  declare `identity_types: [posix]` (or list it beside `okta`); `validate`
+  refuses an image whose group resolves to an identity type its base does
+  not declare.
+- **No credentials, no network, no state.** The builders read the
+  configuration only.
+
+## Configuration reference
+
+A group builder and a user builder, in `cfg/group-builders.yml`:
+
+```yaml
+group_builders:
+  - name: posix-local
+    type: posix
+    shell: /bin/bash        # the login shell of this builder's users (default)
+    admin_sudo: true        # the group's admins get NOPASSWD sudo (default)
+user_builders:
+  - name: posix-users
+    type: posix
+```
+
+| Builder field | Type | Default | Meaning |
+|---|---|---|---|
+| `shell` | str | `/bin/bash` | the login shell given to accounts this plugin creates |
+| `admin_sudo` | bool | `true` | a group's `admins` may run anything as root without a password (their accounts have none: keys only); `false` leaves sudo to the operator |
+
+A group of a posix builder declares its id as `gid:`; a user of a posix user
+builder declares `uid:` and its keys as `public_keys:`:
+
+```yaml
+groups:
+  - name: pxgroup
+    type: posix-local
+    gid: 3101
+    members: [taylor_tango, uma_uniform]
+    admins: [taylor_tango]
+users:
+  - name: taylor_tango
+    type: posix-users
+    first_name: Taylor
+    last_name: Tango
+    uid: 3201
+    public_keys: ["ssh-ed25519 AAAA... taylor@example.invalid"]
+```
+
+The ids, checked at `validate` (the core's `check_posix_ids`, over the
+claims both builders make):
+
+- every posix group declares a `gid:` and every posix user a `uid:`, each at
+  least 1024 (below that are the system's own accounts; the `Group` model
+  refuses a lower gid when it loads, and the check holds uids to the same
+  floor);
+- a user's private group takes the user's name and uid, so a declared group
+  of the same name with another gid is refused, naming both;
+- two groups with one gid, or two users with one uid, are refused;
+- names are POSIX names a machine accepts: lower case, a letter or
+  underscore first, at most 32 characters, `.`, `_` and `-` allowed.
+
+A posix group or user that declares `attributes:` is refused: the ids are
+`gid:` and `uid:`, not provider attributes.
+
+## What it tests and verifies
+
+- **In the bake** (the base image's in-bake checks): the four commands
+  exist; for an instance image, the owning group stands with its gid
+  (`getent group <name>`).
+- **At `validate`**: the id rules above, every one named with the sides
+  that disagree; and every member or admin of a posix group must be a
+  user of a posix user builder with a `uid:` (the accounts the script
+  creates).
+- **Its tests**: [`tests/test_posix_accounts.py`](tests/test_posix_accounts.py)
+  holds the script's parts as text and checks the whole script parses;
+  the system's `tests/test_v2_posix_identity.py` holds the builders, the
+  id resolution and the generated IaC; the container leg of `just
+  full-test` runs the script on AlmaLinux 10 and Debian, twice, against an
+  equal and a differing pre-existing group.
+
+## When it fails
+
+| Symptom | Meaning | Do |
+|---|---|---|
+| `group <g>: no side supplies its id ... declare one (gid:)` at `validate` | a posix group or user without an id | declare `gid:` (group) or `uid:` (user) |
+| `group <g>: the configuration supplies id <a> and the configuration (user-private group) supplies <b>` | a declared group shares its name with a posix user | rename one; a user's private group is the user's name |
+| `groups <a>, <b> all have id <n>` | two names, one id | give each its own |
+| `posix accounts: group <g> has gid <x> here; the configuration says <y>` in a bake's output (exit 3) | the base image already has that group with another gid | change the declared gid, or the base |
+| `posix accounts: gid <n> belongs to group <h> here; the configuration gives it to <g>` (exit 3) | the base image already uses that gid for another group | choose a free gid |
+| `command -v visudo` fails in a base bake | the family lacks sudo | install it in the OS builder's packages |
+| `posix group <g>: <u> has no posix account` at `validate` | a member or admin of a posix group is not a posix user with a uid | declare it on a `type: posix` user builder with a `uid:`, or take it out of the group |
+| `Instance <i>: the accounts script of group <g> FAILED (exit <n>)` in a run's log, with the script's `posix accounts:` lines above it | the machine refused (a group or user standing with another id) or could not be reached | read the lines; fix the id or the machine; the next applying run tries again |
+| `login proof <i>: proof key: FAILED -- CSIS_PROOF_SSH_KEY is not set` | the proof user's private key is not in the environment (CI: the secret is unset) | set the secret, or take `is_service_account` off if no proof is wanted |
+| `login proof <i>: tunnel: FAILED -- the runtime gives no ssh tunnel to <i>` | the machine is not running, or the runtime has no session mechanism | start it, or declare the runtime's `session_mechanism` |
+| `login proof <i>: login: FAILED -- ssh <u>@<i> id: exit 255 ...` | the key was refused, or the tunnel could not open (AWS: `ssm:StartSession` on `AWS-StartSSHSession`, the session-manager plugin). In CI the tail names the role: the proof runs under the WRITE identity since stage 89, and a workflow from before 0.1.1.dev22 made it under the read-only role, which may not open a session | read the tail; check the key pairs with `public_keys:` and the role's grant; in CI, take the release whose workflow makes the proof before the read-only identity is taken back |
+| `login proof <i>: in its group: FAILED` | the account stands but is not in the group | an applying instance run brings membership back; read its accounts log |
+| `Instance <i>: <u> has no account here yet; not a member of <g> until it does` (a warning) | a member's account does not stand yet | nothing: the next run adds it once the account exists |
+| `identity: group '<g>' was managed by the system but is missing from the YAML` at `validate` | a posix group was deleted from the YAML; a group the system once managed never leaves it (DESIGN N19) -- met 2026-10-04 retiring the live proof's group | put the entry back with `unmanaged: true` and no members; its gid stays claimed by the name, and nothing on any machine is touched |