Will be available in version 2.71.1

In order to support a more flexible solution for identity based access management, not tied to complex product structures, Assets are new solution that will enable clients to specify what the user has access to themselves, without any explicit requirements from SPiD.

Via POST /user/{id}/asset/{assetId} endpoint client is able to create (or modify) access to asset for user.

  • {id} can be user_id or UUID
  • {assetId} must be non-numeric identifier see more assetId type

Use cases

Use Cases for handling access checks for NON-SPiD assets are many:

  • check if you have access to a specific purchased e-book
  • check if you have purchased a Finn-ad addon
  • check if you have paid for an account upgrade
  • check if you have access to a restricted feature (like p2p enabling or disabling users on the client)
  • check if you have access to some product not currently defined in the SPiD product structure because the product structure doesn’t match the client’s product structure requirements
  • check if you have access to a specific news article


Do you have questions, or just want to contribute some newly gained insight? Want to share an example? Please leave a comment. SPiD reads and responds to every question. Additionally, your experience can help others using SPiD, and it can help us continuously improve our documentation.