<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Thingy52 provisioning OOB blinking public key</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56687/thingy52-provisioning-oob-blinking-public-key</link><description>Hello. 
 
 I have question about output OOB and public key. 
 I create my Android app for Thingy Bluetooth mesh purposes. I would like to start output OOB process (then Thingy blinks couple of times). 
 Shoud I generate before this blinking process, a</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 Jan 2020 13:49:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56687/thingy52-provisioning-oob-blinking-public-key" /><item><title>RE: Thingy52 provisioning OOB blinking public key</title><link>https://devzone.nordicsemi.com/thread/231674?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 13:49:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff894d93-996e-425f-9adf-105144334c04</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have documented the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.0.0%2Fmd_doc_getting_started_provisioning_procedure-api.html"&gt;Provisioning process and API&lt;/a&gt; in the nRF5 SDK for Mesh documentation on Infocenter. The message sequence chart shows the provisioning process for both nodes, while separate sections below describe the full provisioning sequence for provisioner and for provisionee. In particular, what you ask for is the provisionee &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.0.0%2Fmd_doc_getting_started_provisioning_procedure-api.html&amp;amp;anchor=provisioning_provisionee_auth"&gt;Step 5: Authenticating the provisioning procedure&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Private and public keys are generated on both devices, and provided when initializing a provisioning context structure with &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.0.0%2Fgroup__NRF__MESH__PROV.html&amp;amp;anchor=ga4cb043c9fb1096e8c77fb6aad13e221d"&gt;nrf_mesh_prov_init()&lt;/a&gt;. This is needed both for provisioner and for provisionee, and the keys are used (in each end) together with the OOB data, as part of the provisioning process. The details are then handled by our mesh stack when you use the provisioning API as described in the &amp;quot;Provisioning process and API&amp;quot; documentation mentioned in the above paragraph.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>