<?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>Implement the authentication procedure at application level?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2327/implement-the-authentication-procedure-at-application-level</link><description>Hi all, 
 I have a devicewith display and only want a specific smartphone with my APP to connect to it. 
 I implement the authentication procedure at application level by adding a custom Service/Charateristics and checking for a changeable password</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Apr 2014 01:56:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2327/implement-the-authentication-procedure-at-application-level" /><item><title>RE: Implement the authentication procedure at application level?</title><link>https://devzone.nordicsemi.com/thread/9600?ContentTypeID=1</link><pubDate>Fri, 25 Apr 2014 01:56:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:905e2d49-c9c7-42c3-bfaa-174082bbd5ad</guid><dc:creator>Juliane</dc:creator><description>&lt;p&gt;I want to achieve authorization with my APP rather than the phone,and other APP can&amp;#39;t get my data of device .&lt;/p&gt;
&lt;p&gt;I define my own service and characteristics to achieve this ,app send request and I generate the one-time password on display.But i dont&amp;#39;t konw how can i generate the one-time password,can you help me ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Implement the authentication procedure at application level?</title><link>https://devzone.nordicsemi.com/thread/9599?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 14:21:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ac9342c-a89c-438c-942f-299802baea6b</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;There are many ways to do this, depending on&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Which side is doing the authentication&lt;/li&gt;
&lt;li&gt;The control you have of each device&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I would probably design a feature using GATT authorization. The initiating side could send a read request to an authorized characteristic value on the peer side, letting the peer application retrieve the return value from RAM/flash or even user input before sending it back. The value could then be used as a challenge, and challenge-response could be written back to complete the handshake.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m interested in why you do not want to use the BLE authentication procedures though. Is it because of security implications, or does this have to fit into an already existing application? OOB authentication is often overlooked, and is more secure than just using a 6-digit MITM PIN.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>