Interacting with Rhino Accounts
This guide discusses all the steps needed to interact with Rhino Accounts within Rhino.
Rhino Accounts is an authentication and authorization system built and supported by Robert McNeel & Associates. It is built on top of the OpenID Connect protocol.
As a brief summary, the authentication services of Rhino Accounts enables you, the developer, to verify an individual’s identity and access (with the user’s permission) account information such as their name, email addresses, profile picture, and more. This allows you to tailor your experience for the user or learn more about who is using your product.
The authorization services are based on OAuth 2 Tokens. A token allows you to access any services that use Rhino Accounts for authorization, including your own. For example, your web server might accept certain files to be uploaded and downloaded from your plugin that sync accross different machines. An authorization token can be obtained by your plugin and can be presented to your web server when uploading or downloading files. The web server can check with Rhino Accounts that the token is valid and the individual it belongs to.
For a more thourough overview of Rhino Accounts, please see the Rhino Accounts Reference.
Taking advantage of Rhino Accounts within Rhino is simple, and requires the following steps to be implemented.
To take Advantage of Rhino Accounts within Rhino:
- Contact us to obtain a unique client id and secret for Rhino Accounts. This will represent your service within the system.
TryGetAuthTokensto retrieve authentication and authorization tokens.
- (Optional) Call
RevokeAuthTokenAsyncto invalidate an authorization token when you no longer need it..