Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Password Prompt #13

Open
betty02 opened this issue Dec 13, 2017 · 3 comments
Open

No Password Prompt #13

betty02 opened this issue Dec 13, 2017 · 3 comments

Comments

@betty02
Copy link

betty02 commented Dec 13, 2017

Working great, took my smart group down from 67 to 7. Just having an issue with the final 7. I flushed all policies on one of the offending machines, watched it do it's thing. Checked in, popped up, pressed OK and then no password prompt?

So jumped on Casper Remote and tried to push the script and the error I get for all of them is as follows -

"Running script ReIssue FileVault Recovery Key...

Script exit code: 1
Script result: [ERROR]: Remote users are logged in.
Error running script: return code was 1.
Submitting log to https://jss.*****.com/
Finished."

Not really sure how to fix the error? Remote users are logged in? The normal user is logged in same as all the others? It shows the first popup fine just doesn't prompt password one? As said worked on the previous 60 all OK!

Any ideas?

Thanks

@mpanighetti
Copy link
Contributor

The remote user was you running Casper Remote. I believe the script exits when there's a remote connection to prevent someone malicious from attempting to intercept credentials or recovery keys.

@betty02
Copy link
Author

betty02 commented Dec 13, 2017

Hmmm think I get it. Even if I don't CR it. The same happens? What's the plan to get around this?

@homebysix
Copy link
Owner

@betty02 - Mario is correct, it's checking for remote users as a security precaution (see #4). However, you can simply disable that check if you prefer. That would mean removing lines 72-77.

I'd be curious to see the output of this command on one of the Macs on which you encountered this error:

/usr/bin/who | grep -Eo '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants