Could not get security token - token.dat
-
01.06.2015 13:00 RegistryHandler 64 bit registry detected
01.06.2015 13:00 Client-Info Version: 0.8.0
01.06.2015 13:00 CommunicationHandler URL: http://192.168.1.14/fog/management/other/ssl/srvpublic.crt
01.06.2015 13:00 CommunicationHandler ERROR: Could not get security token
01.06.2015 13:00 CommunicationHandler ERROR: Die Datei “C:\Windows\system32\token.dat” konnte nicht gefunden werden.Is there after the update to svn3495 something to do?
greetings
Michael
-
That error will always occur on the first run. As long as it still authenticates you are fine. What concerns me is the CA cert issue in the logs. It seems the handshake public key is missing. Tom will be able to help you regenerate it
-
@Jbob I’m having a similar issue…this output is from a vm that I registered and deployed sysprep to via Quick Image…
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 11/8/2015 12:52 AM Client-Info Version: 0.9.5 11/8/2015 12:52 AM Middleware::Communication URL: http://10.72.3.50/fog/management/other/ssl/srvpublic.crt 11/8/2015 12:54 AM Middleware::Authentication ERROR: Could not get security token 11/8/2015 12:54 AM Middleware::Authentication ERROR: Could not find file 'C:\Windows\system32\token.dat'. 11/8/2015 12:54 AM Data::RSA CA cert found 11/8/2015 12:54 AM Middleware::Authentication Cert OK 11/8/2015 12:54 AM Middleware::Communication POST URL: http://10.72.3.50/fog/management/index.php?sub=authorize 11/8/2015 12:54 AM Middleware::Communication Response: Invalid security token 11/8/2015 12:54 AM Bus Registering ParseBus in channel Power
This is after a reboot, which I’m assuming should succeed.
Fedora 22 SVN 5229 client 9.5
Token.dat is not present under /windows/system32 this after I reset encryption data
-
@Hanz The client will not have a security token until after the first successful authentication. The problem is that the server doesn’t seem to be doing “Reset encryption data” right. Paging @Tom-Elliott
-
@Jbob I’d also like to add that I had an existing cert from FOG, but something other than FOG CA…it was dated from 9/2015 thru 9/2025. I deleted this “old” cert as it could have been from my previous FOG server that was Ubuntu based. Now I guess there is a possibility that this old cert is on some of my machines as well, causing issues with authentication. I’ll look into this further.
-
This seems to be relating to the ca in the first place. If the ca is from September did you change the ca recently? The error, as I see it, is not a validation of the server but literally the security token is out of sync.
-
@Tom-Elliott yes i went from Ubuntu to fedora and started over basically(for which I’m thankful). Any new install, I thought, created a new cert…I reinstalled once before with the -c to create a new cert…not knowing that it was disastrous… Jbob gave me a snap-in to repin, and that makes everything ok on older clients, circa first server, now it seems like fresh installs need repinned.
-
Same here :
I’ve fresh install a new FOG server (only restore image / image group association), and I have that error on a fresh client installation (new PC installed - never had FOG client before)
------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 17/11/2015 15:37 Client-Info Version: 0.9.7 17/11/2015 15:37 TaskReboot Running... 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/service/servicemodule-active.php?moduleid=taskreboot&mac=00:50:56:AA:28:16||00:00:00:00:00:00:00:E0&newService=1 17/11/2015 15:37 Middleware::Communication Response: Success 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/service/jobs.php?mac=00:50:56:AA:28:16||00:00:00:00:00:00:00:E0&newService=1 17/11/2015 15:37 Middleware::Communication Response: Invalid host certificate 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/management/other/ssl/srvpublic.crt 17/11/2015 15:37 Middleware::Authentication ERROR: Could not get security token 17/11/2015 15:37 Middleware::Authentication ERROR: Impossible de trouver le fichier 'C:\Windows\system32\token.dat'. 17/11/2015 15:37 Data::RSA FOG Server CA cert found 17/11/2015 15:37 Middleware::Authentication Cert OK 17/11/2015 15:37 Middleware::Communication POST URL: http://172.20.0.4/fog/management/index.php?sub=authorize 17/11/2015 15:37 Middleware::Communication Response: Invalid host certificate ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 17/11/2015 15:37 Client-Info Version: 0.9.7 17/11/2015 15:37 HostnameChanger Running... 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:50:56:AA:28:16||00:00:00:00:00:00:00:E0&newService=1 17/11/2015 15:37 Middleware::Communication Response: Success 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/service/hostname.php?moduleid=hostnamechanger&mac=00:50:56:AA:28:16||00:00:00:00:00:00:00:E0&newService=1 17/11/2015 15:37 Middleware::Communication Response: Invalid host certificate 17/11/2015 15:37 Middleware::Communication URL: http://172.20.0.4/fog/management/other/ssl/srvpublic.crt 17/11/2015 15:37 Middleware::Authentication ERROR: Could not get security token 17/11/2015 15:37 Middleware::Authentication ERROR: Impossible de trouver le fichier 'C:\Windows\system32\token.dat'. 17/11/2015 15:37 Data::RSA FOG Server CA cert found 17/11/2015 15:37 Middleware::Authentication Cert OK 17/11/2015 15:37 Middleware::Communication POST URL: http://172.20.0.4/fog/management/index.php?sub=authorize 17/11/2015 15:37 Middleware::Communication Response: Invalid host certificate
-
@ch3i See this post, might clear things up
https://forums.fogproject.org/topic/6130/certificate-issues-since-moving-fog-from-ubuntu-to-fedora
No issues with this after 5374
-
@Hanz Thx I’ll test, I’m on 5360