JEA is difficult for delegates to use without tab completion
By default tab completion is disabled in JEA endpoints- and there is no guidance on how (or if) it can be enabled safely.
Without tab completion it is
1. Harder to discover available commands (no Get-<tab>)
2. Harder to execute available commands with correct parameter name spelling etc.
3. Harder to populate correct values (e.g., no help with ValidateSet scenarios)
This all works against the applicability of JEA for delegation scenarios where a less expert sub-admin has to blindly type out a potentially complex and unfamiliar command.
Please make some basic level of tab completion work by default, and please provide guidance around tab completion and endpoint safety so we don't accidentally undermine the security boundary while adding or modifying tab completion in the field.
Ashley McGlone (GoateePFE) commented
All you have to do is allow the TabExpansion2 function in the role definition. Works just fine. Am I missing something?
Andrew Pearce commented
Is there any plans around timelines that can be shared for this? The idea of JEA, to provide supporting staff the ability to perform white-listed actions on servers almost necessitates tab completion.
Glad to see the response! This would be a huge help for our organization as we want to start delegating rights with JEA to teams that haven't spent much time with PowerShell yet.
Ryan Puffer commented
Thanks for the feedback, Matthew.
We agree and are already looking into ways to bring tab completion to JEA sessions in a future release. I can't commit to a timeline, but promise it's on our radar.