FOG 1.5.0 active directory domain password auto-encryption not working
Fog_Rob last edited by
Good day all,
I’ve a new FOG setup here with ubuntu 16.04 64bit and FOG 1.5.0
I importated the database from previous fog 1.3 and this feature was working.
now on 1.5.0 when I type a password, it is not encrypted after I hit update?
when I select show/hide, it shows the password not encrypted.
maybe it is how it works, but the computers are not being moved to AD so something is wrong.
If anybody can help, would be nice to share solution.
@larosejm as of 1.5, that field is no longer encrypted in the database, but is still encrypted while in transit to the client.
@Tom-Elliott pehaps we should remove the “will auto encrypt” label as it could be misleading.
larosejm last edited by
@fog_rob I am experiencing this issue as well, not related to clients whatsoever, the web interface just doesn’t auto-encrypt the plaintext password in the web interface.
@Fog_Rob each FOG server has a unique identity that a client will “lock into”. Since you changed physical servers, your clients are expecting your old server’s identity.
See this wiki article for how to make your new sever have your old one’s identity
Fog_Rob last edited by
@tom-elliott Hi, I found the problem, it is the old fog client on images, and all the computer’s client are not communicating cause I don’t have login history since I moved to this new fog server :( even if they upgrated automatically to the .11.15 from this fog?
I uninstalled the old .11.14 client and intalled the new .11.15 and it worked on my test machine that I was trying to join to domain from a fresh deployement and it worked.
this in painfull because i’ll have to rebuild all my images with the new client …
I there a way to correct this other than to find a way to push/force the new client on all computers from fog server (I think automatic client update doesn’t work properly)?
Fog_Rob last edited by Fog_Rob
@tom-elliott Hi Tom, I hope this is what you want, fog.log from a client machine that doesn’t work?
If not, please explain how to get that error log. Thanks!
Client error logs please? The field is no longer encrypted when stored to the dB as the passed data is encrypted.
Wayne Workman last edited by
Asking @tom-elliott to look at this.