One of the early conclusions on security from testbed 13 is that when using OAuth in combination with a desktop application there is a need to register the desktop client with identity providers (such as NASA or dutch Kadaster) in a user friendly way. That is to say the user needs to take no action to achieve client registration. OAuth has a mechanism for this called dynamic client registration where trust between client and idp can be established once for each client (e.g. QGIS, Arcmap etc...) bij the software vendor. Without dynamic client registration each end user has to actively register his instance of client software which is very user unfriendly. The idea would be to try out dynamic client registration in practice with a service provided for instance by dutch kadaster.
One of the early conclusions on security from testbed 13 is that when using OAuth in combination with a desktop application there is a need to register the desktop client with identity providers (such as NASA or dutch Kadaster) in a user friendly way. That is to say the user needs to take no action to achieve client registration. OAuth has a mechanism for this called dynamic client registration where trust between client and idp can be established once for each client (e.g. QGIS, Arcmap etc...) bij the software vendor. Without dynamic client registration each end user has to actively register his instance of client software which is very user unfriendly. The idea would be to try out dynamic client registration in practice with a service provided for instance by dutch kadaster.