Skip to content

Users

In order to login to MIKE OPERATIONS, a user name is needed.

By default, the "admin" user is available.

This user has administrator rights in MIKE OPERATIONS. Administrators can create users and workspaces as well as assigning users to a workspace.

New users can be created in the System Explorer using the context menu of the Users node.

  • User name
    The name of the user, specified when logging in to MIKE OPERATIONS.
    When using DHI single sign-on, the user name should be the e-mail address of the user in DHI Azure.
  • Full Name
    The full name of the user.
  • Administrator
    A value indicating whether the user is administrators.
    Administrators can create users create other users, create namespaces and associate users to workspaces.
  • Trusted Account
    A trusted Windows account that has trust relation with the log on user.
  • User Type
    The user type:
    • Native authentication
      Password is specified on the user in MIKE OPERATIONS.
    • Active Directory authentication
      The Windows account specified is used for authentication. For Active Directory authentication, no password is stored on the user in MIKE OPERATIONS.
    • DHI single sign-on
      It's also possible to authenticate using DHI Azure Active Directory. DHI Azure Active Directory uses Microsoft's enterprise cloud-based identity and access management (IAM). This is the same system that is used to log in to DHI's cloud platform (e.g., DataAdmin).
      If authenticating using DHI Azure Active Directory, the User Name is the same as the DHI Azure user name. The password is handled by Azure Active Directory and therefore not stored in the MIKE OPERATIONS database. In this way, authentication is like using Windows Active Directory.
      It is not necessary to authenticate using DHI Azure Active Directory to access data stored in DHI cloud storage. If the user is signed in to Azure Active Directory, any database login (e.g., admin) will have the same access to data stored in DHI's cloud platform.
  • E-mail
    Optional e-mail of the user.
  • Password
    The password for the user when using Native authentication. The password should contain at least 8 characters.
    It is recommended to use a strong password though.
    A strong password:
    • Has 12 Characters, Minimum: You need to choose a password that’s long enough. There’s no minimum password length everyone agrees on, but you should generally go for passwords that are a minimum of 12 to 14 characters in length. A longer password would be even better.
    • Includes Numbers, Symbols, Capital Letters, and Lower-Case Letters: Use a mix of different types of characters to make the password harder to crack.
    • Isn’t a Dictionary Word or Combination of Dictionary Words: Stay away from obvious dictionary words and combinations of dictionary words. Any word on its own is bad. Any combination of a few words, especially if they’re obvious, is also bad. For example, “house” is a terrible password. “Red house” is also very bad.
    • Doesn’t Rely on Obvious Substitutions: Don’t use common substitutions, either — for example, “H0use” isn’t strong just because you’ve replaced an o with a 0. That’s just obvious.