Update Network and Application key at start of KeyUpdate

[eanderlind]

Is there a way for application to create updates of NetworkKey and ApplicationKey for use in KeyUpdate procedure?
The api in

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Mesh API/MeshNetwork+Keys.swift

Line 74 in 78b532d

func add(applicationKey: Data, withIndex index: KeyIndex? = nil, name: String) throws -> ApplicationKey {

recreates a key at same index, while we instead want to invoke the (internal access) didSet on the existing key.
The same api also limits binding to the first Netkey, however it looks like once we have an Appkey we can rebind it using

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Mesh API/ApplicationKey+NetworkKey.swift

Line 40 in 78b532d

func bind(to networkKey: NetworkKey) throws {

Hopefully just didn't find correct api.

[philips77]

Hi,
Yes, it is possible. For that you have to send ConfigNetKeyUpdate or ConfigAppKeyUpdate message to [local Node](

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/MeshNetworkManager.swift

Line 643 in 78b532d

func sendToLocalNode(_ message: ConfigMessage) throws -> MessageHandle {

, just like to any other Node.

The message will be handled here:

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Layers/Foundation Layer/ConfigurationServerHandler.swift

Lines 139 to 145 in 78b532d

	if networkKey.phase == .normalOperation {
	// Update the key data (observer will set the `oldKey` automatically).
	networkKey.key = request.key
	// And mark the key in the local Node as updated.
	localNode.update(networkKeyWithIndex: keyIndex)
	}
	return ConfigNetKeyStatus(confirm: networkKey)

Setting the key in line 141 does the following:

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Mesh Model/NetworkKey.swift

Lines 94 to 104 in 78b532d

	public internal(set) var key: Data {
	willSet {
	oldKey = key
	oldNetworkId = networkId
	oldKeys = keys
	}
	didSet {
	phase = .keyDistribution
	regenerateKeyDerivatives()
	}
	}

The update(networkKeyWithIndex sets the updated flag in the Node's key list:

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Mesh Model/Node.swift

Lines 748 to 756 in 78b532d

	/// Marks the Network Key in the Node as updated.
	///
	/// - parameter networkKeyIndex: The Network Key index to add.
	func update(networkKeyWithIndex networkKeyIndex: KeyIndex) {
	if let key = netKeys[networkKeyIndex] {
	key.updated = true
	meshNetwork?.timestamp = Date()
	}
	}

[philips77]

You may find some info here: #314

[eanderlind]

Thanks - that explains the 2nd half of the process. The remaining part is how to instantiate the two messages with the new key. Looks like only way is to generate a newkey bytestring and then hand craft a msg using the ConfigNetKeyUpdate(parameters:Data) initializer.

IOS-nRF-Mesh-Library/nRFMeshProvision/Classes/Mesh Messages/Foundation/Configuration/ConfigNetKeyUpdate.swift

Line 50 in 78b532d

public init?(parameters: Data) {

Not intuitive, but we will try it out... Thanks. Closing the issue since there is a workaround.

[philips77]

Great that you pointed it out. That needs improvement. I'll fix it in the next (big!) release.

[philips77]

@eanderlind I fixed the API. The 2 config messages now allow to pass the new key as Data.