Title | Text |
---|---|
Access Level Authorization | A Soda user obtains authorization to work at an access level by logging in and selecting one of the access levels that they are entitled to have. Their entitlements are set by source administrators. When a Soda user runs a program that uses the Soda API, the API methods execute at the user's access level. When a program uses the Virtual Data Lake API, it can present a credential with its secret key to execute at the access level associated with the credential. Source administrators can manage credentials. |
Access Level Entitlements | A source admin can authorize a user to have an access level in two ways:
A source admin can add, edit or remove an identity entitlement, and can add, edit or remove a provider-level entitlement. |
Add an Identity Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Edit an Identity Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Remove an Identity Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Add a Provider-Level Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Edit a Provider-Level Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Remove a Provider-Level Entitlement | On the Access Level page for an access level, when logged in with source admin access level:
|
Credentials | A credential is a resource that is associated with an access level and can be used by a program to execute a virtual data lake API method at that access level. It is represented by an item in the same source as the access level that it is associated with. To gain authorization to execute at the access level, the program presents the credential with a secret key. Credentials are managed by source admins. |
Credentials Admin | A credential that is associated with an access level provides authorization for a program to execute at that access level. A source admin can create and delete credentials, and generate their secret keys. The secret keys are displayed to the admin when they are generated, but cannot be retrieved after that. They are not stored in the virtual data lake. Hash digests are stored in the virtual data lake, and are used to validate keys supplied to API calls. |
Create a Credential | On the Access Level page for the access level that the credential will be associated with, when logged in with source admin access level:
|
Delete a Credential | On the Access Level page for the access level that the credential is associated with, when logged in with source admin access level:
|
Generate a Secret Key | A secret key is generated automatically when a credential is created. You may wish to generate a new key periodically, as a security measure. You may also wish to generate a new key if the previous one is lost. When a new key is generated, it is effective immediately, and the previous one immediately becomes invalid. To generate a secret key, on the Access Level page for the access level that the credential is associated with, when logged in with source admin access level:
|