jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

Setup Manager 1.4 - Single Touch workflow with Jamf Pro and Jamf Connect - Issue #12

New Issue
Closed
opened 2026-01-19 18:31:14 +00:00 by michael · 4 comments
michael commented 2026-01-19 18:31:14 +00:00
Owner
Copy Link

Originally created by @shak-h1 on GitHub.

Following the instructions and configuring the Single Touch workflow with Jamf Pro and Jamf Connect. Once the email has been inputted and JSM has completed. The Jamf Connect Login window shows this 'Hello . Please re-enter your password'. It does not show the users name and therefore the password does not work. However when looking at the device record in Jamf it is populated with the users information. This is only occurring with version 1.4.

Originally created by @shak-h1 on GitHub. Following the instructions and configuring the Single Touch workflow with Jamf Pro and Jamf Connect. Once the email has been inputted and JSM has completed. The Jamf Connect Login window shows this 'Hello . Please re-enter your password'. It does not show the users name and therefore the password does not work. However when looking at the device record in Jamf it is populated with the users information. This is only occurring with version 1.4.
michael added the bug label 2026-01-19 18:31:14 +00:00
michael commented 2026-01-19 18:31:14 +00:00
Author
Owner
Copy Link

@antzinoz commented on GitHub:

Can confirm the issue in my current testing

@antzinoz commented on GitHub: Can confirm the issue in my current testing
michael commented 2026-01-19 18:31:14 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

we have confirmed this is happening with 1.3.1 with a newer version of Jamf pro. this is probably a change in the jamf binary.

As a workaround, we can confirm that inserting a waitForUserEntry in the enrollmentActions works, until we find a better solution

@scriptingosx commented on GitHub: we have confirmed this is happening with 1.3.1 with a newer version of Jamf pro. this is probably a change in the jamf binary. As a workaround, we can confirm that inserting a **`waitForUserEntry`** in the **`enrollmentActions`** works, until we find a better solution
michael commented 2026-01-19 18:31:14 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

Still trying to figure out what is happening here.

Does it help if you insert a waitForUserEntry action in the list of enrollmentActions?

@scriptingosx commented on GitHub: Still trying to figure out what is happening here. Does it help if you insert a **waitForUserEntry** action in the list of **enrollmentActions**?
michael commented 2026-01-19 18:31:14 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

please test with 1.4.1 release

@scriptingosx commented on GitHub: please test with [1.4.1 release](https://github.com/jamf/Setup-Manager/releases/tag/v1.4.1)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?