Reference documentation and code samples for the Identity Access Context Manager v1 API enum ServicePerimeter.Types.PerimeterType.
Specifies the type of the Perimeter. There are two types: regular and
bridge. Regular Service Perimeter contains resources, access levels, and
restricted services. Every resource can be in at most ONE
regular Service Perimeter.
In addition to being in a regular service perimeter, a resource can also
be in zero or more perimeter bridges. A perimeter bridge only contains
resources. Cross project operations are permitted if all effected
resources share some perimeter (whether bridge or regular). Perimeter
Bridge does not contain access levels or services: those are governed
entirely by the regular perimeter that resource is in.
Perimeter Bridges are typically useful when building more complex toplogies
with many independent perimeters that need to share some data with a common
perimeter, but should not be able to share data among themselves.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe content provides reference documentation for the \u003ccode\u003ePerimeterType\u003c/code\u003e enum within the Google Identity Access Context Manager v1 API, specifically for .NET.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003ePerimeterType\u003c/code\u003e can be either \u003ccode\u003eRegular\u003c/code\u003e or \u003ccode\u003eBridge\u003c/code\u003e, with a \u003ccode\u003eRegular\u003c/code\u003e perimeter containing resources, access levels, and restricted services, while a \u003ccode\u003eBridge\u003c/code\u003e only contains resources.\u003c/p\u003e\n"],["\u003cp\u003eA resource can belong to one regular service perimeter and zero or more perimeter bridges, but all resources affected by a cross-project operation must share at least one common perimeter.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes links to different versions of the API, ranging from version 1.2.0 to the latest version 2.5.0, allowing for version-specific information retrieval.\u003c/p\u003e\n"],["\u003cp\u003eThe fields in the enum \u003ccode\u003ePerimeterType\u003c/code\u003e include \u003ccode\u003eBridge\u003c/code\u003e, described as "Perimeter Bridge", and \u003ccode\u003eRegular\u003c/code\u003e, described as "Regular Perimeter".\u003c/p\u003e\n"]]],[],null,[]]
