Zum Hauptinhalt springen

Permissions

Veröffentlicht am 27. Juni 2019· Aktualisiert am 28. Juni 2019

Cover image for: Permissions

The permissions resource describes what a key, and therefore its users, can access. For example, a key might be configured to have the source_type:icloud.account scope which allows its users to create sessions against iCloud accounts.

Every permission is constrained by what the base permissions of the organisation are. It is not possible to create permissions which are beyond what the organisation has access to.

Attributes

nametypedescription
idpermission IDResource identifier.
resourcestring, always permissionResource type specifier.
organisationorganisation IDThe organisation these permissions are associated with.
scopesdictionaryThe scope to which the permission applies.

Scopes

The scopes attribute defines what the permissions grant access to. Scopes look like source_type:icloud.account, which would grant permission to create iCloud account sources.

Each scope can have associated limits. These act as restrictions on the permissions granted by the scope. For example, the source_type:icloud.account scope might have a limit:

{
  "level": "user",
  "type": "count",
  "value": 3
}

This would restrict the number of iCloud account sources a user can create to a maximum of three.

The format of the scopes attribute, give the example above, would be:

{
  "source_type:icloud.account": [
    {
      "level": "user",
      "type": "count",
      "value": 3
    }
  ]
}

Scopes can also include simple wildcards, like task_type:icloud.* which gives permission to use any tasks related to the iCloud service.

Scope types

  • source_type gives access to specific source types.
  • task_type gives access to specific task types.
  • data_type gives access to specific data types.
  • file_type gives access to specific file types.

Limits

nametypedescription
levelstringOne of: organisation, key, or user.
typedictionaryThe scope to which the permission applies.

A limit can act at one of three different levels: organisation, key, or user. This determines how broadly the limit is applied. For example, a scope may have a limit which restricts the organisation to only 10 iCloud accounts (an organisation level limit) and another limit that restricts each user within that organisation to just 2 iCloud accounts each (a user level limit).

There are three types of limits: count, interval, and inflight. The count type is absolute (i.e. the total count of iCloud accounts every accessed), while interval takes the count over a period of time (i.e. 1 iCloud account per month), and inflight is a concurrency limit (i.e. can only poll 1 iCloud account at a time).


Verwandte Artikel

Brauchst du Hilfe?

Wir bemühen uns, alle Nachrichten innerhalb eines Werktags zu beantworten.

support@reincubate.com
Logo des King's Award for Enterprise

King's Award for Enterprise: Reincubate hat die höchste offizielle Wirtschaftsauszeichnung des Vereinigten Königreichs viermal gewonnen, zuletzt in Anerkennung des herausragenden Wachstums des Unternehmens in den vergangenen drei Jahren.

Unsere Beziehungen zu Nutzern und Partnern stehen im Mittelpunkt unserer Werte und der Produkte, die wir entwickeln. Lies unsere Bewertungen, um zu erfahren, was sie über uns sagen.

Nach ISO 27001 zertifiziert durch das Centre for Assessment, akkreditiert durch UKAS

© 2008-2026 Reincubate Ltd. Alle Rechte vorbehalten. Eingetragen in England und Wales unter der Nr. 5189175, USt-IdNr. GB151788978. Camo®, Streamlight® und Reincubate® sind eingetragene Marken. Patente angemeldet.

Hilfe