Last modified on 16 December 2019, at 13:14

Configure Users and User Rights

Revision as of 13:14, 16 December 2019 by NWE (Talk | contribs)

In many projects, it is important to distinguish the active user, mainly for the mobile client. Mostly, it is required to just restrict access to certain users. Often, there are also different groups of users that should have different rights to view, edit, create or delete objects. In some cases, the content provided to the mobile client should depend on the active user. This How-To explains how to configure users and how to customize a UBIK® application depending on the active user.

Managing user accounts

The first step in any case is to create and organize accounts for users. In some case, users have to be imported from an external system, which is best done using Proxies (see also how to Configure Proxies). However, accounts can also be created manually or programmatically. In any case, the following information is relevant.

Login

In UBIK®, an account object is called Login, with the system MetaClass LOGIN. Theoretically, a user can have multiple such login credentials, but normally, you'd have one per user. If there are multiple logins for one user, you can create a custom meta class for the users and link the login objects to them via the CONSUMER Reference property (see also how to Relate Objects). You can also create a derivation of the LOGIN system meta class to add further details for the instances. A login object has the following important properties:

  • LOGINNAME: The account name
  • DOMAINNAME: The domain name
  • SYSADMINRIGHTS: Whether the user has administrator privileges in UBIK® Studio
  • USE_DOMAIN_CREDENTIALS: Whether to use Active Directory for authentication
  • PASSWORD: The password
  • CONSUMER: A link to the person this login is associated with (useful if there are multiple accounts per person)

So, the steps to create a login are:

  1. Find the system meta class LOGIN and drag it into a new bulk editor.
  2. Create a new instance, filling in at least the LOGINNAME, the DOMAINNAME and the PASSWORD.
  3. Save the new instance.

User groups

Login accounts are best managed in groups corresponding to roles, e.g., "Administrator" or "Engineer". This is important if you don't want to distinguish by account individually, but more generally by their role. This allows you to add new logins (to existing groups) without having to adapt your customizing. There is a system meta class USERGROUP that can be used for this. Similar to the way you would link multiple logins to a user, you can also relate multiple users to one or many groups (there is a system relation for that, SYSREL_GROUP_LOGIN).

If you have just one group of users (i.e., all the users have the same rights or highly individual rights), it is not necessary to configure groups.

The steps to create and apply a group are:

  1. Find the system meta class USERGROUP and drag it into a new bulk editor.
  2. Create a new instance, filling in the name
  3. Save the new instance.
  4. Drag the new group into a relation browser.
  5. Find the login(s) you want to associate with the group and drag it onto the relation node for SYSREL_GROUP_LOGIN (relation between groups and logins).
  6. Save the changes.



See also