<?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>Connection and Passkey</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26660/connection-and-passkey</link><description>In my application, a static passkey is given to the user(I have implemented static pass key in my application and it is working). 
 Suppose the Nordic device is advertising and some random user (who doesn&amp;#39;t have a static key) connects with the peripheral</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Nov 2017 09:32:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26660/connection-and-passkey" /><item><title>RE: Connection and Passkey</title><link>https://devzone.nordicsemi.com/thread/104880?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 09:32:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7aebd978-2749-4f11-9aed-02669f64c89c</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The only way to limit connections, is to use whitelisting. If you have an existing bond, you can whitelist the identity address (or the identity resolving key (IRK) if you are using Privacy). A common implementation is to always whitelist when there is an existing bond, and allow the user to clear all bonds by button press. An alternative is to do whitelisted, connectable advertising until a button is pressed, then have a few seconds of non-whitelisted advertisements so new peers can bond. Please note that the maximum amount of whitelisted peers is 8 in the most recent softdevices, and that you need to store the bonding information for each of them locally.&lt;/p&gt;
&lt;p&gt;An alternative implementation is to immediately send a security request to the peer upon connection. If the peer does not respond to the pairing within a certain time-frame, you can call disconnect and go back to advertising.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>