Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
zarchasmpgmr
2 months agoNew Contributor
CLI using Windows Hello on subsequent uses
Environment:
- Win11
- PowerShell (various versions)
- Regina Rexx program which invokes CLI via ADDRESS COMMAND (here's the outlier)
1P settings:
- Security
- Unlock using Windows Hello
- Show Windows Hello prompt automatically
- Use TPM
- Confirm password interval set
- Auto-lock interval set for 1 week (machine is in home office and generally is shut off over the weekend, this is fine for my working environment)
- Developer
- CLI integrated
- Environment:
- OP_BIOMETRIC_UNLOCK_ENABLED="true" set by the Regina Rexx script
The first time it's run after startup, I receive the password prompt, whether or not I've already entered it for another use of 1P. The password prompt text is the normal "password needed before using Windows Hello". Subsequent CLI calls from the program don't trigger authentication pop-ups. On subsequent runs, even within a minute, I am asked to authenticate with password again.
My desired experience is that I should only receive the password prompt after startup (whether it's from the app or CLI), and then just receive Windows Hello authentication as triggered.
As a silverback software developer, the only thing that pops into my mind is that the authentication scope is limited to the specific execution of the program. I have set the BIOMETRIC environment variable at the shell level before executing Regina and that doesn't change the behavior. So, I figure I'm missing something, and someone more familiar with the ecosystem might have good suggestions.
Thanks in advance,
Ray
So it's been four weeks of traveling. In the meantime, I read deeper into the doc and found that it's WAD, authentication is at the process level, which of course is good design. I would have to spin off a process to run everything under (or play semaphore games) to get what I want, and it isn't worth the investment.
If this pops up in anyone's search results, know that it's WAD.
2 Replies
- zarchasmpgmrNew Contributor
So it's been four weeks of traveling. In the meantime, I read deeper into the doc and found that it's WAD, authentication is at the process level, which of course is good design. I would have to spin off a process to run everything under (or play semaphore games) to get what I want, and it isn't worth the investment.
If this pops up in anyone's search results, know that it's WAD.
- zarchasmpgmrNew Contributor
I'll be on the road next week, so I won't be able to try things until I return.