- Jamf Nation Community
- Products
- Jamf Connect
- SecureToken issue and new login screen
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-27-2022 10:05 AM
Hi All
Im having some issues with SecureToken not being assigned, therefore FileVault is never enabled. I created a policy users can run and that will use the admin account and assign a securetoken to the new user. This has been working just fine but now I have a user with a machine that has changed the login process since assigning the securetoken
Old workflow:
boot up, jamf connect appears, enter email and password, then verify network password and your in
New workflow:
reboots, asked to select admin or his account , selects his account, is prompted for network password then jamf connect appears
I havent changed anything in the process of workflow since creating the policy months back
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2022 02:54 PM - edited 05-12-2022 02:55 PM
So i figured out that the user was not explaning this correctly, jumped on a zoom and confirmed it is the FV unlock screen at reboot. This is normal once FV2 is enabled on machines.
Jamf Connect is a very good product in my opinion for keeping account password in sync locally and through your directory. I dont agree completely with every password being a possible issue, you just need to make sure that you have jamf connect sync setup correctly in the config profile. I can say that managing passwords without Jamf Connect was not fun especially with AD binded macs
The SecureToken issue is ultimately caused because a boostrap token isn't found for the machine, I think its an apple issue at that point and not Jamf
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-12-2022 06:38 AM
following out of interest ( I do not currently have Connect) .. but I thought one of the big sell points of connect is the accounts would then be local, hence having a security token. I guess if one of these accounts did not get a security token that probably would have put me full stop till that issue was resolved.
Another sys admin (that knows nothing about apple devices) kind of referred me to this leaching of the local admin security token method while I was trying to argue for the purchase of Connect, and tested showed every password change has the potential to cause serious issues with this approach (that was really intended for parents to be able to be to control encryption on kids accounts)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2022 02:54 PM - edited 05-12-2022 02:55 PM
So i figured out that the user was not explaning this correctly, jumped on a zoom and confirmed it is the FV unlock screen at reboot. This is normal once FV2 is enabled on machines.
Jamf Connect is a very good product in my opinion for keeping account password in sync locally and through your directory. I dont agree completely with every password being a possible issue, you just need to make sure that you have jamf connect sync setup correctly in the config profile. I can say that managing passwords without Jamf Connect was not fun especially with AD binded macs
The SecureToken issue is ultimately caused because a boostrap token isn't found for the machine, I think its an apple issue at that point and not Jamf
