Usecase: Only a single GPIO is in the configuration; as output and active low(recipe configuration).
WPE_IOCONNECTOR_PINS = "507:output:true"

Issue: Plugin activation fails with the following log.
Jul 20 06:29:57 HP40A /usr/bin/WPEFramework[5949]: [Mon, 20 Jul 2020 06:29:57 ]:[PluginServer.cpp:403]: Startup: Activation of plugin [IOConnector]:[IOConnector], failed. Error [Could not instantiate the requested Pin]

Depending on server implementation DHCP ACK not necessarily contains a ROUTE option. RFC only states that options in ACK should not be in conflict with OFFER. If the route option is missing from ACK, the NetworkControl plugin tries to set the GW to the DHCP address. If the Gateway address differs from the DHCP server address, this will fail and it results that the client has no internet connection.

If SSID contains non-ascii characters, they are converted to utf-8 and escaped to hexadecimal escape sequences.
In old RDK wifi-hal, this is unescaped by printf_decode provided by wpa_supplicant.

There seems to be two READMEs for Security Agent
https://github.com/rdkcentral/ThunderNanoServices/blob/master/SecurityAgent/doc/SecurityAgentPlugin.md
Seems to not have documentation on the acl configuration parameter as well as docs around what the ACL file looks like.
https://github.com/rdkcentral/ThunderNanoServices/blob/master/SecurityAgent/SecurityAgentPlugin.md
Has documentation on ACL list, however the documentation is not correct. In the acl file it has the field groups, however it should be assign.
https://github.com/rdkcentral/ThunderNanoServices/blob/master/SecurityAgent/AccessControlList.h#L194
The example ACL json also has the wrong value groups
https://github.com/WebPlatformForEmbedded/ThunderNanoServices/blob/master/SecurityAgent/example_acl.json
It also might be helpful in the docs to say where the acl file should go. Looking into the source I was able to find out it is in the plugin's persistent path /root/SecurityAgent