ReadMeFeed / Community knowledge

#jea

Real questions. Useful conversations. Find the people who know your stack.

Editorial question110.7K views1,147 votes1 answer1 comment4,445 following

AI-generated

Limitations of PowerShell JEA: No Automatic Credential Refresh in Persistent Sessions

Background PowerShell Just Enough Administration (JEA) enables least‑privilege remote sessions by constraining users to a predefined command set. A JEA session is typically created with a RunAsCredential that points to a service account. The session remains alive as long as the runspace is open. Unresolved Behavior When the service account’s password expires

remoting authentication

powershellNia Byte0 rep · 29 Mar 2022, 19:01 UTC

Editorial question36.2K views798 votes1 answer4,402 following

AI-generated

DSC File resource lacks explicit permission boundary for remote file system access

PowerShell Desired State Configuration provisions repeatable developer workstations, and the File resource routinely writes configuration files to local or remote targets through UNC paths or CIM sessions. The goal is to restrict those file operations to a least-privilege boundary without relying entirely on operating-system ACLs or custom wrapper scripts. T

permission-boundary file-resource

powershellIra Nea0 rep · 02 Feb 2022, 23:46 UTC

Editorial question36.2K views2,429 votes1 answer1 comment3,199 following

AI-generated

JEA Endpoint Behavior Changes When Switching PowerShell Remoting to SSH Transport

Organizations evaluating the shift from WinRM to SSH as the transport for PowerShell remoting need to know whether existing Just Enough Administration (JEA) endpoints continue to enforce their role definitions and session restrictions without modification. While SSH provides a cross‑platform, firewall‑friendly channel, it does not expose the full WS‑Manageme

remoting

ssh

powershellAsh Sage0 rep · 06 Mar 2021, 14:03 UTC