Skip to main content
Skip to content

MySecuritySettings

No description

type MySecuritySettings {
  followIdentityEmail: Boolean!
  heldPasswordKind: String
  loginMethods: [ViewerLoginMethod!]!
  mfaEnforcement: String!
  mfaMethods: [ViewerMfaMethod!]!
  passwordChangeSupported: Boolean!
  passwordKind: String
  passwordLink: PasswordLink!
  passwordRules: PasswordRules
  requiresCurrentPassword: Boolean!
}

Fields​

MySecuritySettings.followIdentityEmail ● Boolean! non-null scalar​

MySecuritySettings.heldPasswordKind ● String scalar​

The kind of the caller's own Owlie password, "standard" or "opaque"; null when they hold none. One of the other kind than passwordKind still signs them in, and that sign-in converts it; it can't be changed here (Owlie can't verify a Secure Login password from a session), so My settings says to sign in with it once or use Forgot password.

MySecuritySettings.loginMethods ● [ViewerLoginMethod!]! non-null object​

MySecuritySettings.mfaEnforcement ● String! non-null scalar​

MySecuritySettings.mfaMethods ● [ViewerMfaMethod!]! non-null object​

MySecuritySettings.passwordChangeSupported ● Boolean! non-null scalar​

The change form for passwordKind applies: Owlie credentials is on and the caller holds no Owlie password or one of that kind.

MySecuritySettings.passwordKind ● String scalar​

The kind of Owlie password the tenant writes, "standard" or "opaque" (Secure Login); null while Owlie credentials is off. The change form shown is this kind's.

The caller's password link: whether password changes reach linked accounts, and which ones now.

MySecuritySettings.passwordRules ● PasswordRules object​

The tenant's password rules; null while Owlie credentials is off.

MySecuritySettings.requiresCurrentPassword ● Boolean! non-null scalar​

The Standard change form asks for the current password, typed and checked on the server: the tenant writes Standard passwords and the caller holds one (the step-up dialog offers the password for the same reason). A Secure Login holder (heldPasswordKind "opaque") proves theirs with a fresh Secure Login sign-in in the change's own requests (opaque.changeStart / opaque.changeFinish) instead.

Returned By​

mySecuritySettings query