MaliciousEntity
Entity whose actions triggered a Gmail phishing alert.
JSON representation |
{
"entity": {
object (User )
},
// Union field entity_type can be only one of the following:
"fromHeader": string,
"displayName": string
// End of list of possible types for union field entity_type .
} |
Fields |
entity |
object (User )
The actor who triggered a gmail phishing alert.
|
Union field entity_type . Every malicious entity could only belongs to one entity type. entity_type can be only one of the following: |
displayName |
string
The header from display name.
|
User
JSON representation |
{
"emailAddress": string,
"displayName": string
} |
Fields |
emailAddress |
string
Email address of the user.
|
displayName |
string
Display name of the user.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-22 UTC.
[null,null,["Last updated 2024-08-22 UTC."],[[["A malicious entity is defined, with JSON representation, and potential entity types (fromHeader or displayName)."],["A malicious entity details the actor triggering a Gmail phishing alert, such as the sender's email address or display name."],["The content describes a User object with attributes including email address and display name, representable in JSON."],["The User object is the entity whose actions led to a Gmail phishing alert, as indicated by the provided context."]]],["The document outlines the structure of data related to entities triggering Gmail phishing alerts. This data includes a representation of the `entity` object, which can be a `User`, and can have either a `fromHeader` (sender's email) or a `displayName`. The `User` object itself contains an `emailAddress` and a `displayName`, representing the user's email and displayed name. Each entity belongs to a single entity type.\n"]]