As we can see that under one node many accounts are produced to make it more sensible add the feature like private key or password. So, user can be authorized by the account library only. I know it can be handled on application-level also but adding features like this can make more secure to access cordapp.
Can generate a private key from name or UUID at the time of the creation of account. And add one more function to verify the account. So, we can verify by library function only(function which returns boolean value by verifying the keys).
There is one more question
If we can have a private key feature then how it can be handled with different node and registered accounts with them?
More suggestions are admired
As we can see that under one node many accounts are produced to make it more sensible add the feature like private key or password. So, user can be authorized by the account library only. I know it can be handled on application-level also but adding features like this can make more secure to access cordapp. Can generate a private key from name or UUID at the time of the creation of account. And add one more function to verify the account. So, we can verify by library function only(function which returns boolean value by verifying the keys).
There is one more question If we can have a private key feature then how it can be handled with different node and registered accounts with them? More suggestions are admired