OBJECT

User

User type. Users are defined in CSP and this type has fields from CSP together with additional semantics from Ensemble

link GraphQL Schema definition

  • type User implements Node {
  • # The account identifier string used by the user to log in. Users might not
  • # necessarily use their email.
  • userAccount: String
  • # Unique user ID - this is the immutable identifier of a user
  • userId: String
  • # The actual email to contact the user. This field doesn't always equal to the
  • # 'username'
  • email: String
  • # The first name of the user.
  • firstName: String
  • # Opaque globally scoped identifier of this node
  • id: ID!
  • # The last name of the user.
  • lastName: String
  • organizationRoles: [UserOrganizationRole!]
  • # The below fields are also in the CSP type but I didn't think it useful to expose
  • # through graphql - we may wish to do so later.
  • #
  • # "The identity provider (IdP) domain of the user. The value will be 'vmwareid' in
  • # case the user is VMware ID user."
  • #
  • # domain: String
  • #
  • # "The user's Identity Provider Identifier."
  • #
  • # idpId: String
  • #
  • # "User is inaccessible if it will not be able to login with it's VMware ID
  • # credentials. Since the user is federated and will be redirected to it's Identity
  • # Provider."
  • #
  • # accessible: Boolean
  • serviceRoles: [UserServiceRole!]
  • # Array of user preferences. Each user pref would specify the entity and a list of
  • # user preferences. Only populated for current user.
  • userPrefs: [UserPref!]
  • # username as in CSP, eg joe.smith@acme.com. This is deprecated in CSP and
  • # replaced by userAccount. Please use email field for user's email.
  • username: String! @deprecated( reason: "replaced by userAccount" )
  • }

link Require by