Rudder

If you want to invalidate a state of the key of a Node (from Certified to Unknown) to allow to change a key of a Node it's impossible.

The status is correctly unset but the algorithm on the server side still use the old key...

Something is fishy in that algorithm, I think we should not use the already saved key in that case but the inventory one (see https://github.com/Normation/ldap-inventory/blob/4.3.8/inventory-api/src/main/scala/com/normation/inventory/services/provisionning/CheckInventoryDigest.scala#L176)