<?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>How to set device security level mode1, level4</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97086/how-to-set-device-security-level-mode1-level4</link><description>hi I am configuring a BLE peripheral using NCS v2.2.99-dev3 and the nRF5340 DK. I want to set the security level of the device to mode1, level 4 for cyber security. I searched several tickets to get the information, but the security level change is failing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Feb 2023 22:45:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97086/how-to-set-device-security-level-mode1-level4" /><item><title>RE: How to set device security level mode1, level4</title><link>https://devzone.nordicsemi.com/thread/412372?ContentTypeID=1</link><pubDate>Mon, 27 Feb 2023 22:45:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32b85658-b674-4f36-a099-69a86e2e620a</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;First of all, for numeric comparison to work, you need a display and buttons to confirm or reject the&amp;nbsp;passkey on&amp;nbsp;&lt;/span&gt;&lt;em&gt;both&lt;/em&gt;&lt;span&gt;&amp;nbsp;devices. If the peripheral only has a display, the standardized approach would be to display the passkey on the peripheral and enter the passkey on the central, assuming you have a keyboard capable of inputting digits on the central. You can of course just fake this and always accept on the peripheral, as it seems to me is what you&amp;nbsp;intend to do, but that is not directly supported or described in the Bluetooth specification.&amp;nbsp;From a firmware perspective, it does not matter much if the input comes from the real-world or internally though, so it&amp;nbsp;is&amp;nbsp;fine with regard to the implementation. Try to use&amp;nbsp;&lt;/span&gt;&lt;span&gt;bt_conn_auth_pairing_confirm&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;auth_conn&lt;/span&gt;&lt;span&gt;&lt;span&gt;); instead of&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;bt_conn_auth_passkey_confirm&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;auth_conn&lt;/span&gt;&lt;span&gt;);.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Amanda H.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>