CC2642R: Authorization and Notifications?

Alexander Wenner

Part Number: CC2642R

Hi.

I would like to use authorization on some of the characteristics in my application to block access until some protocol has been followed. However, some of these characteristics also generate notifications, which only authorized devices should receive. Do the standard TI mechanisms for notifications contain some check that blocks notifications to not yet authorized devices? I've looked at the implementation of GATTServApp_ProcessCharCfg and the most I could find is a flag requiring authentication.

Sincerely,

Alex

over 4 years ago

0 desouza over 4 years ago

TI__Guru**** 171074 points

Alex,

I would take a look at the following topics of our Simplelink Academy training:

Task 2 of the Security Fundamentals module:

https://dev.ti.com/tirex/explore/node?node=AOPOY.GDApakIOYjiwoY6A__pTTHBmu__LATEST

Task 3 of the Advanced Security module:

https://dev.ti.com/tirex/explore/node?node=AFERPlObnVsqfYjOysBF5w__pTTHBmu__LATEST

Hope this helps,

Rafael

0 Alexander Wenner over 4 years ago in reply to desouza

Intellectual 420 points

Hi Rafael,

thank you for the links. However, my question was specifically concerning the interaction between setting a characteristic to GATT_PERMIT_AUTHOR_READ, in addition to GATT_PERMIT_AUTHEN_READ, and notifications. Especially whether some automatic checks happen behind the scenes when generating notifications for such characteristics.

However as far as I can tell after further experiments, that is not the case. I am going to add manual calls to the authorization callback in addition to setting the flag for requiring an authenticated link before triggering a notification.

Sincerely,

Alex

Bluetooth®︎

Bluetooth forum

CC2642R: Authorization and Notifications?