Topics created by eseo-fcolas

@eseo-fcolas Unfortunately this is a known issue but needs major work which we don’t have time for at the moment: https://github.com/FOGProject/fog-client/issues/116

If you are keen to get this to work you are more than welcome to join in and work on this part of FOG/fog-client.

The other thing I might suggest is that most Linux systems can be configured to pull hostname settings via DHCP. You might want to look into this. Or you can use FOG post-deploy scripting to modify hostname config files on the destination system before doing the first reboot.

Thanks for your answer.

I suggest to reserve /bin/bash to Linux or Mac. Then when booting on Windows, the client could just ignore it (keeping it in queue) because it’s bash.

@tom-elliott yes, Zm9nOnBhc3N3b3Jk (default fog:password), as you can see on screenshot. I’m also create new user, enable API for him and get same result.

And same result with curl:

[root@ ~]# curl -H 'fog-api-token: <token>' -u fog:password -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'Authorization: Basic Zm9nOnBhc3N3b3Jk' -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'fog-user-token: <token>' -X GET http://<fog-ip>/fog/system/status **success**

Only auth with two tokens work fine.