Configure passwords for automatically created user accounts

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Configure passwords for automatically created user accounts

    This document outlines how to configure passwords for user accounts automatically created from incoming emails in ServiceNow. Utilizing theglide.email.inbound.usedefaultpasswordandglide.user.defaultpasswordsystem properties, administrators can control password creation for these accounts, provided the instance is set up to receive emails and enable automatic user creation.

    Show full answer Show less

    Prerequisites

    • Your instance must be configured to automatically create new user accounts.
    • A POP3 server must be set up to store and receive email for your instance.
    • The glide.email.read.active system property must be set to true.
    • The glide.pop3readerjob.createcaller property must also be set to true to allow automatic user creation.
    • If glide.pop3readerjob.createcaller is false, skip the glide.user.defaultpassword property.

    Key Features

    In versions Quebec and earlier, new user accounts receive a complex default password from the glide.user.defaultpassword property, requiring users to change it upon first login. In the Rome release and later, the default behavior changes, allowing users to create their password via the "Forgot Password?" link instead of being assigned one. The behavior can be altered using the glide.email.inbound.usedefaultpassword property:

    • true: New accounts use the default password defined in the glide.user.defaultpassword property.
    • false: New accounts do not have a default password; users must set their password upon first access.

    Key Outcomes

    By properly configuring these properties, administrators can ensure that user accounts created from incoming emails are secure and adhere to the organization's password policies. This enhances the overall security posture of the ServiceNow instance while providing users with a straightforward account setup experience.

    Use the glide.email.inbound.use_default_password and glide.user.default_password system properties to define how to create passwords for new users created from incoming emails.

    The system properties described in this document define how the instance handles passwords for user accounts generated from incoming emails. Your instance needs to be configured with the ability to receive emails and to enable automatic user creation. See the section below for details on those configurations.

    After your instance is configured to create accounts automatically, you can use the properties to determine whether to use a default password and define that password, if needed.

    Prerequisites

    To use these properties, your instance must be configured to automatically create new user accounts.
    • You must configure your own POP3 server to store and receive email for your instance. Then, you must set the glide.email.read.active system property to true. To learn more about configuring a POP3 server on your instance, see Enable using your own POP3 server.
    • Set the glide.pop3readerjob.create_caller property to true. With this property change, your instance can automatically create users from incoming email. To learn more, see Enable automatic user creation.
      Note:
      Skip the glide.user.default_password property if the glide.pop3readerjob.create_caller property is set to false.

    How your instance defines passwords

    In Quebec and earlier releases of ServiceNow, your instance creates new user accounts from incoming emails using a complex password defined in the glide.user.default_password system property. Users use this password the first time they log in, and then, the instance prompts the user for a new password. If you have upgraded your instance to Rome or later releases, this process remains unchanged. As an administrator, you can update your instance to use the new method described below.

    In new instances beginning with the Rome release, user accounts created from incoming emails do not have a password. When a user first accesses the instance with their new account, they must enter their user name and click on the Forgot Password? button to create an initial password.

    In Rome and later releases, you can choose which process your instance follows by setting a value in the glide.email.inbound.use_default_password system property. To change from the default behavior described above, create this system property using the following information:

    System property field Value
    Name glide.email.inbound.use_default_password
    Type true|false
    Value Select a value based on your desired behavior:
    true
    New accounts use a default password defined in the glide.user.default_password system property.
    false
    New accounts do not have a default password. Users must define a password, as described earlier in this section.
    For more detail on creating system properties, see Add a system property.

    Define a default password

    If your instance is configured to use a default password, you must define that password using the glide.user.default_password system property. Create this property using the following information:

    System property field Value
    Name glide.user.default_password
    Type password2
    Value Enter a unique password to use as a default. Use strong password complexity to help ensure the security of your instance.