Will Authentec Truesuite be updated for 10.9?

Also, the only problem with the TrueSuite is that it can't log you in (as if that were small), but all other aspects of the software work fine, so there's no reason to uninstall the entire Suite, just disable the option that lets you use the suite to log you in as a user.

That option is found in the System Preferences -> TrueSuite, Options tab, turn off "Fingerprint Log On"

Hope this helps.

I couldn't login to any of my accounts but could do a ssh to my frozen login mac. So I opened AppDelegate.scpt (see Frobitz66) in another Mac with applescript and did all the removes line by line the script would have done on the remote session (ssh). After a final reboot, the loginwindow crashed by the following:

Oct 24 09:14:56 rmac-lan.fritz.box airportd[217]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "?|??".

Oct 24 09:14:57 --- last message repeated 1 time ---

Oct 24 09:14:57 rmac-lan.fritz.box SecurityAgent[2790]: Failed to create agent mechanism, failing authentication!

Oct 24 09:14:57 rmac-lan.fritz.box com.apple.authd[37]: engine[2778]: error creating mechanism agent

Oct 24 09:14:57 rmac-lan.fritz.box com.apple.authd[37]: engine[2778]: evaluate returned -60008 returning errAuthorizationInternal

Oct 24 09:14:57 rmac-lan.fritz.box loginwindow[2778]: Login Window - Returned from Security Agent

Oct 24 09:14:57 rmac-lan.fritz.box UserEventAgent[2783]: Failed to copy info dictionary for bundle /System/Library/UserEventPlugins/alfUIplugin.plugin

Oct 24 09:14:57 rmac-lan.fritz.box loginwindow[2778]: ERROR | -[LoginApp performAuthPluginRequest:] | AuthorizationRef doesn't have a username. Exiting.

Oct 24 09:14:57 rmac-lan.fritz.box WindowServer[2779]: CGXRestartSessionWorkspace: session workspace exited for session 256 (on console)

Oct 24 09:14:57 rmac-lan.fritz.box WindowServer[2779]: Session 256 released (1 references)

Oct 24 09:14:57 rmac-lan.fritz.box WindowServer[2779]: Session 256 released (0 references)

Oct 24 09:14:57 rmac-lan.fritz.box WindowServer[2779]: loginwindow connection closed; closing server.

The problem is the : error creating mechanism agent and this came from the changed authorization in mavericks. Now it is in /var/run/auth.db (which is a sqlite3 DB):

security authorizationdb read system.login.console

showed a:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>class</key>

<string>evaluate-mechanisms</string>

<key>comment</key>

<string>Login mechanism based rule. Not for general use, yet.</string>

<key>created</key>

<real>404205825.35804099</real>

<key>mechanisms</key>

<array>

<string>builtin:policy-banner</string>

<string>tssc_agent:lion_login</string>

<string>builtin:login-begin</string>

<string>builtin:reset-password,privileged</string>

<string>builtin:forward-login,privileged</string>

<string>builtin:auto-login,privileged</string>

<string>builtin:authenticate,privileged</string>

<string>PKINITMechanism:auth,privileged</string>

<string>builtin:login-success</string>

<string>loginwindow:success</string>

<string>HomeDirMechanism:login,privileged</string>

<string>HomeDirMechanism:status</string>

<string>MCXMechanism:login</string>

<string>loginwindow:done</string>

</array>

<key>modified</key>

<real>404205827.82298797</real>

<key>shared</key>

<true/>

<key>tries</key>

<integer>10000</integer>

<key>version</key>

<integer>1</integer>

</dict>

</plist>

YES (0)

Note the tssc line in it which came from the truesuite software. In /System/Library/Security there is a authorization.plist which is the basis for the auth.db in /var/db. So I moved /var/db/auth.db out of the way and rebooted.

Now I'm back again.

I also had the same problem after upgrading to Mavericks without uninstalling the Authentec Suite. Couldn't login anymore, but I just found a solution (it takes 5 minutes, so it's a rather fast solution compared to a restore ;-))

So, if you cannot login anymore due to the Eikon :

1) Boot into single user mode (CMD-S while rebooting)

2) Mount the harddrive, type "/sbin/mount -uw /"

3) Type "rm /var/db/.applesetupdone"

4) type "reboot"

Now, your mac "thinks" it's new and you can configure a new user account just after the reboot (your existing accounts stay untouched).

So create the new account, then go to the Truesuite PrefsPane and in the options, DISABLE "Fingerprint LogOn" (the fingerprint sensor must be connected to do this, else the options will be greyed out),.

Now you can login back to your regular account (and delete the previously created account).

Sorry if this has just been mentioned but I had the same problem with TruSuite. I logged in as Guest and set my usual account to login automatically. After restarting, having first plugged out the scanner, it just logged me right into my account as usual.

I would make the point that over the last year or so, with products, it does seem as if Apple are getting rather "sloppy" and am noticing a failure to deliver that would once never be tolerated.

yreiser, thank you very much. It's realy helps me.

Of course, using the Guest account is easier but I had the Guest account disabled so this was not an option to me.

RGab, your solution is going way over my head and the only problem is I think it's probably the only way I'm going to be able to log back into my computer so could you try and describe it in a way that might make sense to someone who has never done this before? Many thanks.

Ps. Guest login does not show as an option at login and safe mode loupes back to login just as others have described here. Furthermore, my time machine appears to be fracked. So this is not an option either. (A very sad day here).

Good Afternoon yreiser -

Thank you for submitting your solution - it proved to be the method with the least resistance. I was working with the Engineering Team form Apple Support and fixed it using your steps while they were still coming up with a plan. I let know what fixed it and told them to look at this thread to see the number of people who were experiencing it.

Cheers.

Derek

Hello Yreiser,

Thanks. Followed your instructions and was able to create a new user account. Had I not previously removed the true suite icon from my System preferences I'd be fine. Here's where it gets tricky. I was able to login as the new user and download the true suite UnInstaller for the last known OS. It mounted and ran. Thought I had a fix on my hands but in doing this I realize that I've created a bigger problem. Now when I reboot, I get the apple plus an infinite loupe spinning wheel. Fun right? Lol.

My next idea is to boot in target mode and transfer my files, then Reload the OS from a clean disk. If you think of any better ideas please share. Thank you.

Hi Dorje1,

you are right. I reported simply my actions to get back a working macbook. I think the crucial point is the remove of the additional security mechanism in the authorization so if you want to try this first the steps would be:

A) if you are able to login remotely by ssh:

sudo rm /var/db/auth.db

reboot

B) if not

1) Boot into single user mode (CMD-S while rebooting)

2) Mount the harddrive, type "/sbin/mount -uw /"

3) Type "rm /var/db/auth.db"

4) type "reboot"

Regards

Apple's purchase of Authentec was publicly disclosed in the Summer of 2012, so there's nothing confidential about the transaction. Here's a link to an article from the NYT Dealbook:

http://dealbook.nytimes.com/2012/07/27/apple-to-acquire-authentec-for-356-millio n/ The purchase was done in part to acquire the fingerprint biometric authentication that is now embodied in the iPhone 5S.

So, it is ridiculous that OS X Mavericks will not support a technology that has been owned by Apple for over a year. And it is utterly absurd that the same technology now owned by Apple causes major user installation problems on what Apple describes as a minor OS X upgrade - with absoultely no warning whatsoever from Apple.

IMHO, that is an Apple customer service #FAIL.

When acquired AuthenTec -- they did NOT promise to integrate the technology into anything.

You cannot point to any source indicating that they did.

It is unfortunate that technology that worked perfectly under previous OS X, no longer works in Mavericks -- and in fact, in several cases, blocks even traditional logins.

Finger-pointing and declarations of shoulda-coulda will not provide satisfactory solutions.

This community can be part of the ultimate solution: politely ask for support. Stress the renewed importance of security in the Mac platform. And offer to lend your support and patience as Apple engineers, tests, and delivers solutions.

Thanks to everyone who has collaborated and contributed solutions. THANK YOU.

Michael Sidoric

CapMac Users Group

Austin, TX

Thanks RJ -- but Communities is a TEAM EFFORT -- just like Apple.

We all have the same problems and concerns, and by working together we can help each other, while Apple works on solutions.

Apple responds to constructive critique. And based on the interest in this thread, I know Apple has plenty to work on.

Lets all stay in touch here and be sure to share thoughts on Authentec support here:

http://www.apple.com/feedback/

Hello and thanks for the reply. At this point option A does not look feasible as I am pretty sure that I disabled remote login via SSH. Therefore looks like option B is the way to go however would you please be so kind as to explain what this commandline does and once executed what my next steps are after rebooting. Thanks.

At this point in time my iMac is pretty hosed so I don't want to go any further down the rabbit hole unless I know what I'm doing. Thanks again bye.