Full name: projects.locations.datasets.consentStores.consents.activate
Activates the latest revision of the specified Consent
by committing a new revision with state
updated to ACTIVE
. If the latest revision of the specified Consent is in the ACTIVE
state, no new revision is committed. A FAILED_PRECONDITION
error occurs if the latest revision of the specified consent is in the REJECTED
or REVOKED
state.
HTTP request
POST https://healthcare.googleapis.com/v1beta1/{name=projects/*/locations/*/datasets/*/consentStores/*/consents/*}:activate
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Required. The resource name of the Consent to activate, of the form Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "consentArtifact": string, // Union field |
Fields | |
---|---|
consentArtifact |
Required. The resource name of the Consent artifact that contains documentation of the user's consent, of the form Authorization requires the following IAM permission on the specified resource
|
Union field expiration . Optional. Allows setting expiration time for Consents. Expired consents are ignored in access determination methods such as [CheckDataAccess]. This value overrides the expiration duration configured for the consent store. expiration can be only one of the following: |
|
expireTime |
Timestamp in UTC of when this Consent is considered expired. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
ttl |
The time to live for this Consent from when it is marked as active. A duration in seconds with up to nine fractional digits, ending with ' |
Response body
If successful, the response body contains an instance of Consent
.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/cloud-healthcare
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.