In my application, I need to support both private and public profile behavior. For the public profile, I want the joining behavior to be compliant with the rule that the NWK key should always be encrypted with the TC Link key. This behavior is controlled (as far as I can determine) by defining the TC_LINKKEY_JOIN item in the build.
My problem is that I also need to be able to join (in my private profile mode) with preconfigured NWK keys. That doesn't seem to work if the TC_LINKKEY_JOIN item has been defined when the image was built. The APS key transport message in that case would contain all zero's, since the key is already configured on both devices. That is incompatible with the requirements of the TC_LINKKEY_JOIN mode.
So I need a programmatic method of allowing for both behaviors. Is this possible? I experimented with the SAS attribute <UseInsecureJoin> and that did not seem to have an effect.
I suppose I could modify the stack files where this item is checked, but I wanted to verify that there was no other way to achieve the desired behavior.