@@ -65,12 +65,67 @@ class GoogleFirebaseAppcheckV1Service extends \Google\Model
6565 * that service.
6666 */
6767 public const ENFORCEMENT_MODE_ENFORCED = 'ENFORCED ' ;
68+ /**
69+ * The relevant App Check protection is not enforced for the service or
70+ * resource, nor are App Check metrics collected. Though the relevant App
71+ * Check protection is not applied, other applicable protections, such as user
72+ * authorization, are still enforced. An unconfigured protection is in this
73+ * mode by default.
74+ */
75+ public const REPLAY_PROTECTION_OFF = 'OFF ' ;
76+ /**
77+ * The relevant App Check protection is not enforced for the service or
78+ * resource. App Check metrics are collected to help you decide when to turn
79+ * on enforcement. These metrics will show the portion of traffic that is
80+ * deemed invalid by the relevant App Check protection, but that traffic will
81+ * not be rejected until you turn on enforcement. Though the relevant App
82+ * Check protection is not enforced, other applicable protections, such as
83+ * user authorization, are still enforced. Some services require certain
84+ * conditions to be met before they will work with App Check, such as
85+ * requiring you to upgrade to a specific service tier. Until those
86+ * requirements are met for a service, this `UNENFORCED` setting will have no
87+ * effect and App Check will not work with that service.
88+ */
89+ public const REPLAY_PROTECTION_UNENFORCED = 'UNENFORCED ' ;
90+ /**
91+ * The relevant App Check protection is enforced for the service or resource.
92+ * The service or resource will reject any traffic not accompanied by an App
93+ * Check token that is deemded valid by the relevant protection. There are
94+ * some exceptions depending on the service; for example, some services will
95+ * still allow requests bearing the developer's privileged service account
96+ * credentials without an App Check token. App Check metrics continue to be
97+ * collected to help you detect issues with your App Check integration and
98+ * monitor the composition of your callers. While the service is protected by
99+ * App Check, other applicable protections, such as user authorization,
100+ * continue to be enforced at the same time. Use caution when choosing to
101+ * enforce App Check protections. If your users have not updated to a version
102+ * of your app that meets the requirements of the relevant App Check
103+ * protection, their app may stop working. App Check metrics can help you
104+ * decide whether to enforce App Check on your services and resources. If your
105+ * app has not launched yet, you should enable enforcement as soon as you
106+ * verify that your App Check implementation is correct, since there are no
107+ * outdated clients in use. Some services require certain conditions to be met
108+ * before they will work with App Check, such as requiring you to upgrade to a
109+ * specific service tier. Until those requirements are met for a service, this
110+ * `ENFORCED` setting will have no effect and App Check will not work with
111+ * that service.
112+ */
113+ public const REPLAY_PROTECTION_ENFORCED = 'ENFORCED ' ;
68114 /**
69115 * Required. The App Check enforcement mode for this service.
70116 *
71117 * @var string
72118 */
73119 public $ enforcementMode ;
120+ /**
121+ * Optional. This checksum is computed by the server based on the value of
122+ * other fields, and may be sent on update and delete requests to ensure the
123+ * client has an up-to-date value before proceeding. This etag is strongly
124+ * validated as defined by RFC 7232.
125+ *
126+ * @var string
127+ */
128+ public $ etag ;
74129 /**
75130 * Required. The relative resource name of the service configuration object,
76131 * in the format: ``` projects/{project_number}/services/{service_id} ``` Note
@@ -83,6 +138,28 @@ class GoogleFirebaseAppcheckV1Service extends \Google\Model
83138 * @var string
84139 */
85140 public $ name ;
141+ /**
142+ * Optional. The replay protection enforcement mode for this service. Note
143+ * that this field cannot be set to a level higher than the overall App Check
144+ * enforcement mode. For example, if the overall App Check enforcement mode is
145+ * set to `UNENFORCED`, this field cannot be set to `ENFORCED`. In order to
146+ * enforce replay protection, you must first enforce App Check. An HTTP 400
147+ * error will be returned in this case. By default, this field is set to
148+ * `OFF`. Setting this field to `UNENFORCED` or `ENFORCED` is considered
149+ * opting into replay protection. Once opted in, requests to your protected
150+ * services may experience higher latency. To opt out of replay protection
151+ * after opting in, set this field to `OFF`.
152+ *
153+ * @var string
154+ */
155+ public $ replayProtection ;
156+ /**
157+ * Output only. Timestamp when this service configuration object was most
158+ * recently updated.
159+ *
160+ * @var string
161+ */
162+ public $ updateTime ;
86163
87164 /**
88165 * Required. The App Check enforcement mode for this service.
@@ -102,6 +179,25 @@ public function getEnforcementMode()
102179 {
103180 return $ this ->enforcementMode ;
104181 }
182+ /**
183+ * Optional. This checksum is computed by the server based on the value of
184+ * other fields, and may be sent on update and delete requests to ensure the
185+ * client has an up-to-date value before proceeding. This etag is strongly
186+ * validated as defined by RFC 7232.
187+ *
188+ * @param string $etag
189+ */
190+ public function setEtag ($ etag )
191+ {
192+ $ this ->etag = $ etag ;
193+ }
194+ /**
195+ * @return string
196+ */
197+ public function getEtag ()
198+ {
199+ return $ this ->etag ;
200+ }
105201 /**
106202 * Required. The relative resource name of the service configuration object,
107203 * in the format: ``` projects/{project_number}/services/{service_id} ``` Note
@@ -124,6 +220,50 @@ public function getName()
124220 {
125221 return $ this ->name ;
126222 }
223+ /**
224+ * Optional. The replay protection enforcement mode for this service. Note
225+ * that this field cannot be set to a level higher than the overall App Check
226+ * enforcement mode. For example, if the overall App Check enforcement mode is
227+ * set to `UNENFORCED`, this field cannot be set to `ENFORCED`. In order to
228+ * enforce replay protection, you must first enforce App Check. An HTTP 400
229+ * error will be returned in this case. By default, this field is set to
230+ * `OFF`. Setting this field to `UNENFORCED` or `ENFORCED` is considered
231+ * opting into replay protection. Once opted in, requests to your protected
232+ * services may experience higher latency. To opt out of replay protection
233+ * after opting in, set this field to `OFF`.
234+ *
235+ * Accepted values: OFF, UNENFORCED, ENFORCED
236+ *
237+ * @param self::REPLAY_PROTECTION_* $replayProtection
238+ */
239+ public function setReplayProtection ($ replayProtection )
240+ {
241+ $ this ->replayProtection = $ replayProtection ;
242+ }
243+ /**
244+ * @return self::REPLAY_PROTECTION_*
245+ */
246+ public function getReplayProtection ()
247+ {
248+ return $ this ->replayProtection ;
249+ }
250+ /**
251+ * Output only. Timestamp when this service configuration object was most
252+ * recently updated.
253+ *
254+ * @param string $updateTime
255+ */
256+ public function setUpdateTime ($ updateTime )
257+ {
258+ $ this ->updateTime = $ updateTime ;
259+ }
260+ /**
261+ * @return string
262+ */
263+ public function getUpdateTime ()
264+ {
265+ return $ this ->updateTime ;
266+ }
127267}
128268
129269// Adding a class alias for backwards compatibility with the previous class name.
0 commit comments