TwinPermissionsForbiddenError

Thrown on a 403 from the twin-scoped permission surface: the caller can see the twin but does not hold ManageTwinPermissions on it. Distinct from TwinNotFoundError, which is what a twin the caller cannot see at all answers — the surface refuses to confirm such a twin exists.

Hierarchy

• Error
  • TwinPermissionsForbiddenError

Index

Constructors

• constructor

Properties

• errorBody

Constructors

constructor

• new TwinPermissionsForbiddenError(message: string, errorBody?: TwinErrorBody): TwinPermissionsForbiddenError

• Overrides Error.constructor

  Parameters

  • message: string

  • optionalerrorBody: TwinErrorBody

  Returns TwinPermissionsForbiddenError

Properties

publicoptionalreadonlyerrorBody

errorBody?: TwinErrorBody

The server's envelope, when there was one. Its presence is load-bearing: a genuine refusal carries cause: 'InsufficientPermissions', while a Twin service that could not evaluate the request at all (a customer-database lookup that threw, a missing twin feature) falls through to the framework's default forbid handler and answers a 403 with no body. Without this a caller cannot tell "you may not" from "we could not tell", and would report the first.