Developing Custom BLE Authentication - How to protect services/characteristics

[scotzark]

Hi-

In our application we are not using pairing, but instead want to use a proprietary authentication scheme were we right a passkey to an unprotected characteristic and based on that we want to unlock the ability to read/write the other services + characteristics.  What is the best way to do this with the 17.1.0 SDK?  Is there a way to simply update the read_perm / write_perm (SEC security parameters) on the fly?  This would seem to do what we want.  When authenticated we just run SEC_OPEN, and then un-auth'd we change it to something like SEC_JUST_WORKS.  But we are wondering if there is a best practice in place for this already?

thanks,

Scot

[scotzark]

Maybe this is what is needed?

GATTS Read Request with Authorization

This way we can check if each client is authorized before the reply?  Is there an example of how to set this up with the 17.1.0?