<?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>Clarification on Write Auth changes in S13x alpha 8</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11174/clarification-on-write-auth-changes-in-s13x-alpha-8</link><description>Migration document is great - I&amp;#39;d be lost without it. I&amp;#39;m just trying to be sure I understand the two changes for &amp;quot;GATT Server Authorizable Write Commands&amp;quot; and &amp;quot;GATT Server Write Authorization and Peer Data&amp;quot;. 
 If I understand the first one correctly</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 07 Jan 2016 09:13:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11174/clarification-on-write-auth-changes-in-s13x-alpha-8" /><item><title>RE: Clarification on Write Auth changes in S13x alpha 8</title><link>https://devzone.nordicsemi.com/thread/41851?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 09:13:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74958258-e5c9-4ca8-be12-ec24beb7ded1</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Thanks for the confirmation - this actually makes my generic write handling code simpler, which is good news.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Clarification on Write Auth changes in S13x alpha 8</title><link>https://devzone.nordicsemi.com/thread/41850?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 08:03:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e14654b0-089c-46fb-aa45-8dd90081592d</guid><dc:creator>vich</dc:creator><description>&lt;p&gt;Hi RK,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Right, v2 API generates an EVT_WRITE with auth_required flag for ATT Write Cmds and the value is not written by SD into ATT table, Application shall authorize write it explicitly. Details here: &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v2.0.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;link text&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Right, Application shall fill the rest of the auth_params while returning SUCCESS. Yes, it&amp;#39;s to save on persistent memory requirements inside SD when multiple authorizations are pending across active connections. Details here: &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v2.0.0/group___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;link text&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Regards,
Vinayak&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>