SecurityCredentialsCircleProto

Security CredentialsSecurity

GoogleApi.ContentWarehouse.V1.Model.SecurityCredentialsCircleProto

1
out of 10
Minimal
SEO Impact
Represents a Google+ Circle. Currently (12/2011), a Circle is identical to the ContactGroup with matching parameters, but Circle must only be used for true Circles and not other Focus groups, and should be preferred over ContactGroup where applicable. Soon it may become more efficient to check membership in a Circle than in a ContactGroup (see http://go/superglue). Support for this principal type is currently (12/2011) incomplete -- e.g., Keystore does not support it yet (see b/5703421).

SEO Analysis

AI Generated

Related to security features. HTTPS is a ranking signal. This model (Security Credentials Circle Proto) contains 3 attributes that define its data structure. Key functionality includes: Circle ID is unique only relative to the owner's Gaia ID. Currently required.

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture

Attributes

3
Sort:|Filter:
circleIdstring
Default: nilFull type: String.t

Circle ID is unique only relative to the owner's Gaia ID. Currently required.

ownerGaiaIdstring
Default: nilFull type: String.t

The owner of the circle. Currently required.

requiredConsistencyTimestampUsecstring
Default: nilFull type: String.t

If present, then tests for membership in this circle must use data known to be at least as fresh as the given (FBS-assigned) timestamp. See http://go/fbs-consistent-read-after-important-write Before using this, be sure that any service checking authorization against this circle supports checking consistency timestamps. For example, as of 12/2011, Keystore only supports this for the Moonshine configuration, and in others authorization checks will fail if the timestamp is present.