Skip to content

jss-progress.sh Can Hang Indefinitely if No Policy with Trigger Available #8

@rougegoat

Description

@rougegoat

Due to some latency with Jamf, I found that there is a potential situation where a properly scoped Self Service policy with the jss-progress.sh script could hang indefinitely if the policy it calls is no longer in scope. This results in the progress bar window being stuck on screen with no obvious way for the end user to force quit it.

Reproducibility: Anytime the jss-progress.sh policy has a trigger for a policy that does not include the machine the jss-progress.sh policy is being run on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions