Skip to main content
Question

Using Generic Local Accounts With Jamf Connect - Login Window Popup


Forum|alt.badge.img+6

Hi,

We mainly use Jamf Connect with Azure AD for staff and student user accounts on our Macs. However, I'm thinking about using a generic local user account for consultants and guests because it is our school's policy to not create school domain accounts for consultants and guests. When I log into the local user account that I created, the user is logged in successfully, but the Jamf Connect login window pops up asking the user to authenticate to Jamf Connect. This login window can't be closed or ignored, unless I disable the setting "RequireSignIn" in the com.jamf.connect configuration profile plist. By disabling that setting, the login window will still pop up, but now I can close the window and ignore it. Are there any repercussions to disabling this setting? How will that setting affect other Jamf Connect with Azure users if I leave it disabled?

5 replies

Forum|alt.badge.img+16
  • Honored Contributor
  • 329 replies
  • December 2, 2022

It can be done.  The two settings you'll want to look into are MigrateUsersHide for the Login Window and PasswordSyncBlockList for the Menu Bar app.  Adding the account in question into those two should prohibit it from getting associated with a network login when the user initially signs in, and the second one should prevent the menu bar app from popping up automatically while the account is signed in.  More information can be found in the Settings Reference portion of the Jamf Connect documentation.

https://docs.jamf.com/jamf-connect/2.17.0/documentation/Preference_Key_Reference.html 
https://www.jamf.com/resources/product-documentation/jamf-connect-administrators-guide/ 


Forum|alt.badge.img+6
  • Author
  • Contributor
  • 20 replies
  • December 5, 2022
McAwesome wrote:

It can be done.  The two settings you'll want to look into are MigrateUsersHide for the Login Window and PasswordSyncBlockList for the Menu Bar app.  Adding the account in question into those two should prohibit it from getting associated with a network login when the user initially signs in, and the second one should prevent the menu bar app from popping up automatically while the account is signed in.  More information can be found in the Settings Reference portion of the Jamf Connect documentation.

https://docs.jamf.com/jamf-connect/2.17.0/documentation/Preference_Key_Reference.html 
https://www.jamf.com/resources/product-documentation/jamf-connect-administrators-guide/ 


I've tried what you suggested and the Jamf Connect login window still pops up after the local account is signed in.


Forum|alt.badge.img+16
  • Honored Contributor
  • 329 replies
  • December 5, 2022
AHSitguy wrote:

I've tried what you suggested and the Jamf Connect login window still pops up after the local account is signed in.


Those fields are case sensitive, so it will see Admin, admin, and AdMiN as three separate accounts.  You may have to put multiple entries in for each.


Forum|alt.badge.img+6
  • Author
  • Contributor
  • 20 replies
  • December 5, 2022
McAwesome wrote:

Those fields are case sensitive, so it will see Admin, admin, and AdMiN as three separate accounts.  You may have to put multiple entries in for each.


The case sensitivity is correct. What I saw on the Mac under /Users is what I put into the plist. I didn't accidentally capitalize the username.


Forum|alt.badge.img+6
  • Author
  • Contributor
  • 20 replies
  • December 8, 2022
McAwesome wrote:

Those fields are case sensitive, so it will see Admin, admin, and AdMiN as three separate accounts.  You may have to put multiple entries in for each.


When you enter the users into the plist file, do you use the short names or the full user account name as it shows in System Preferences\\Users?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings