Difference between revisions of "Login"

Latest revision as of 11:01, 6 August 2024

The Login Object holds the necessary information for managing logins to UBIK^®. A login represents a possible connection from a user in a certain use case. One user (person) can have several logins, whereas each Login name must be unique. It is possible to define a password for every single Login. A Login can be marked having administrative rights.

Name

The name of the Login object.

The name of a Login object must not include a "\".

Domain Name

The domain name is used to group Logins, where the name of Logins must be unique within one domain.

The domain name of a Login Object must not include a "\".

This information is used for Authentication via Active Directory (if configured).

Use Domain Credentials

If this setting is set to true, UBIK uses the Actvice Directory to verify the login name and password when for authentication.

Login Name

Unique identifier of a Login object. The default value is: Domain Name + "\" + Name

If you enter a value matching this pattern, the domain name and name of the Login are set automtically!

The Login object may only be saved if the Login name is unique!
The Login name must not include more than one "\"!

Password

It is possible to set a password for a Login. Whenever a connection to UBIK^® is established, the connection information (Login-name and password) is validated according the settings of the Login object. If no password is defined, every password for the given Login is valid.

Consumer

Each Login can be assigned to a Consumer - but this is not mandatory. The Consumer object groups a set of Login objects (for example, a human being is a possible Consumer).

If you want to use the multi-tenancy feature, you must link the Login to a Consumer belonging to a tenant!

OS_Types (since UBIK.Server 4.8)

Types of Operating Systems can be configured for each login. Depending on the OS types of the logins, the web service uses the login with the configured os type. If there are no OS types configured (eg. OS_TYPES property is not set) for a login, the login is usable for all existing Operating Systems. When configuring multiple OS types for a login object, the types need to be separated by a semicolon.

Available OS Types:

Unknown = 0
Android = 1
Win10 = 2
Web = 3
X_IOS = 4
X_Android = 5
X_Windows = 6
WinServer = 10
Win10Desktop = 11
HoloLens = 12

Examples:

OS_TYPE of Login for Win10 and Android: 2;5
OS_TYPE of Login for Android: 5

@@ Line 1: / Line 1: @@
-==Basics==
+The Login Object holds the necessary information for managing logins to {{UBIK}}. A login represents a possible connection from a user in a certain use case. One user (person) can have several logins, whereas each Login name must be unique. It is possible to define a password for every single Login. A Login can be marked having administrative rights.
-The Login Object holds the necessary information for managing logins to UBIK. A login represents a possible connection from a user in a certain use case.
+==Name==
-One User (Person) can have severall logins. The Login Name must be unique. It is possible to define a password for every single Login.
+The name of the Login object.
-A Login can be marked as Admin - Login.
+{{Attention|The name of a Login object must not include a "\". {{Version/ServerSince|2.5.0}}}}
-==Consumer==
+==Domain Name==
-The Login knows its [[Consumer]] - but there is no need to have one. The Consumer objet groups a set of Login objects.
+The domain name is used to group Logins, where the name of Logins must be unique within one domain.
-A human being is a possible Consumer.
+{{Attention|The domain name of a Login Object must not include a "\". {{Version/ServerSince|2.5.0}}}}
+This information is used for Authentication via Active Directory (if configured). {{Version/ServerSince|2.6.0}}
+==Use Domain Credentials==
+If this setting is set to true, UBIK uses the Actvice Directory to verify the login name and password when for authentication.
+{{Version/ServerSince|2.6.0}}
+==Login Name==
+Unique identifier of a Login object. The default value is: '''Domain Name + "\" + Name'''
+{{Hint|If you enter a value matching this pattern, the domain name and name of the Login are set automtically! {{Version/ServerSince|2.5.0}}}}
+{{Attention|The Login object may only be saved if the Login name is unique!<br/>The Login name must not include more than one "\"! {{Version/ServerSince|2.5.0}}}}
 ==Password==
-It is possible to set a password for a Login. Whenever a connection to UBIK is established, the connectioninformation (Login-Name and Password) is validated according the settings of the Login object. If no password is defined, every password for the given Login is valid.
+It is possible to set a password for a Login. Whenever a connection to {{UBIK}} is established, the connection information (Login-name and password) is validated according the settings of the Login object. If no password is defined, every password for the given Login is valid.
+==Consumer==
+Each Login can be assigned to a [[Consumer]] - but this is not mandatory. The Consumer object groups a set of Login objects (for example, a human being is a possible Consumer).
+{{Hint|If you want to use the multi-tenancy feature, you must link the Login to a Consumer belonging to a tenant! {{Version/ServerSince|2.5.0}}}}
+==OS_Types (since UBIK.Server 4.8)==
+Types of Operating Systems can be configured for each login. Depending on the OS types of the logins, the web service uses the login with the configured os type. If there are no OS types configured (eg. OS_TYPES property is not set) for a login, the login is usable for all existing Operating Systems. When configuring multiple OS types for a login object, the types need to be separated by a semicolon.
+Available OS Types:
+* Unknown = 0
+* Android = 1
+* Win10 = 2
+* Web = 3
+* X_IOS = 4
+* X_Android = 5
+* X_Windows = 6
+* WinServer = 10
+* Win10Desktop = 11
+* HoloLens = 12
+Examples:
+* OS_TYPE of Login for Win10 and Android: '''2;5'''
+* OS_TYPE of Login for Android: '''5'''
+[[Category:UBIK|Login]]