<?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>Developing Custom BLE Authentication - How to protect services/characteristics</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90390/developing-custom-ble-authentication---how-to-protect-services-characteristics</link><description>Hi- 
 In our application we are not using pairing, but instead want to use a proprietary authentication scheme were we right a passkey to an unprotected characteristic and based on that we want to unlock the ability to read/write the other services +</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 27 Jul 2022 13:31:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90390/developing-custom-ble-authentication---how-to-protect-services-characteristics" /><item><title>RE: Developing Custom BLE Authentication - How to protect services/characteristics</title><link>https://devzone.nordicsemi.com/thread/378934?ContentTypeID=1</link><pubDate>Wed, 27 Jul 2022 13:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0569c7b9-709d-49c4-92c1-97ab4029fe66</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Authorization seems to be the way to go yes, you can add authorization on both read and write, ref:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___r_e_a_d___r_e_q___a_u_t_h___m_s_c.html"&gt;https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___r_e_a_d___r_e_q___a_u_t_h___m_s_c.html&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___w_r_i_t_e___r_e_q___a_u_t_h___m_s_c.html"&gt;https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___w_r_i_t_e___r_e_q___a_u_t_h___m_s_c.html&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___w_r_i_t_e___c_m_d___a_u_t_h___m_s_c.html"&gt;https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v7.3.0%2Fgroup___b_l_e___g_a_t_t_s___w_r_i_t_e___c_m_d___a_u_t_h___m_s_c.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I would think (hope) searching through the ble projects for sd_ble_gatts_rw_authorize_reply() can give some results.&lt;/p&gt;
&lt;p&gt;Edit: Also check out:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/66820/how-to-deal-with-the-characteristic-read-event/273665"&gt;RE: How to deal with the characteristic read event?&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Developing Custom BLE Authentication - How to protect services/characteristics</title><link>https://devzone.nordicsemi.com/thread/378759?ContentTypeID=1</link><pubDate>Tue, 26 Jul 2022 14:47:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0289bbce-d9b3-48db-b7d5-f5b0ecd58047</guid><dc:creator>scotzark</dc:creator><description>&lt;p&gt;Maybe this is what is needed?&lt;/p&gt;
&lt;p&gt;&lt;span&gt;GATTS Read Request with Authorization&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;This way we can check if each client is authorized before the reply?&amp;nbsp; Is there an example of how to set this up with the 17.1.0?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>