Create a method that allows dshub to create a certificate that clients can use to authentify themselves into a hub. This has to be discussed with client developers (if possible to reach a better agreement)
The first question that rises is : The client should use a certificate generated by the hub to login ( signed by the hub's private key ) , but this means a client will have more certificates for each registered hub. This doesn't mean the client's public key changes ( just that it has more certificates for the same key signed by different issuers ). The client should implement such a mechanism . And secondly, there should be an easy way to get the certificates from the hub to the clients. This could be done automatically or manually . Anyway, the client should have in it's favorites tab a field where the user could select what certificate to use for authentication with that specific hub.
I'm waiting for feedback from client developers if this is ok or not with their ideas...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The first question that rises is : The client should use a certificate generated by the hub to login ( signed by the hub's private key ) , but this means a client will have more certificates for each registered hub. This doesn't mean the client's public key changes ( just that it has more certificates for the same key signed by different issuers ). The client should implement such a mechanism . And secondly, there should be an easy way to get the certificates from the hub to the clients. This could be done automatically or manually . Anyway, the client should have in it's favorites tab a field where the user could select what certificate to use for authentication with that specific hub.
I'm waiting for feedback from client developers if this is ok or not with their ideas...