Login - Revision history

LMA at 11:01, 6 August 2024

2024-08-06T11:01:51Z

MHM at 12:18, 8 November 2016

2016-11-08T12:18:18Z

KNO at 15:18, 2 May 2016

2016-05-02T15:18:06Z

KNO at 11:05, 20 October 2015

2015-10-20T11:05:07Z

KNO at 11:04, 20 October 2015

2015-10-20T11:04:48Z

MHM at 09:30, 2 July 2015

2015-07-02T09:30:15Z

MHM at 14:51, 1 July 2015

2015-07-01T14:51:40Z

MHM at 14:50, 1 July 2015

2015-07-01T14:50:46Z

MHM at 14:50, 1 July 2015

2015-07-01T14:50:02Z

MHM at 11:18, 1 July 2015

2015-07-01T11:18:56Z

← Older revision		Revision as of 11:01, 6 August 2024
Line 28:		Line 28:

	{{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}}}}		{{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]]		[[Category:UBIK\|Login]]

@@ Line 8: / Line 8: @@
 The domain name is used to group Logins, where the name of Logins must be unique within one domain.
 {{Attention|The domain name of a Login Object must not include a "\". {{Version/ServerSince|2.5.0}}}}
 ==Login Name==

@@ Line 3: / Line 3: @@
 ==Name==
 The name of the Login object.
-{{Attention|The name of a Login object must not include a "\" ({{Version/ServerSince|2.5.0}})}}
+{{Attention|The name of a Login object must not include a "\". {{Version/ServerSince|2.5.0}}}}
 ==Domain Name==
 The domain name is used to group Logins, where the name of Logins must be unique within one domain.
-{{Attention|The domain name of a Login Object must not include a "\" ({{Version/ServerSince|2.5.0}})}}
+{{Attention|The domain name of a Login Object must not include a "\". {{Version/ServerSince|2.5.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}})}}
+{{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}})}}
+{{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==
@@ Line 22: / Line 22: @@
 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}})}}
+{{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}}}}
 [[Category:UBIK|Login]]

← Older revision		Revision as of 11:05, 20 October 2015
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. 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.

@@ 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.
-One User (Person) can have severall logins. The Login Name must be unique. It is possible to define a password for every single Login.
-A Login can be marked as Admin - Login.
 ==Name==
-The name from the Login object.
+The name of the Login object.
-{{Attention|The name of a Login Object must not include a "\"<br/>{{Version/ServerSince|2.5.0}}}}
+{{Attention|The name of a Login object must not include a "\" ({{Version/ServerSince|2.5.0}})}}
 ==Domain Name==
-{{Version/ServerSince|2.5.0}}<br/>
+The domain name is used to group Logins, where the name of Logins must be unique within one domain.
-The domain name is used to group logins. The Name of logins must be unique within one domain.
+{{Attention|The domain name of a Login Object must not include a "\" ({{Version/ServerSince|2.5.0}})}}
-{{Attention|The domain name of a Login Object must not include a "\"<br/>{{Version/ServerSince|2.5.0}}}}
 ==Login Name==
-Unique Name - Identifier of the login object.<br/>
+Unique identifier of a Login object. The default value is: '''Domain Name + "\" + Name'''
-The login object consists per default of:<br/>
 Domain Name + "\" + Name
-{{Hint|If you enter a value matching this pattern, the domain name and name of the login are set automtically!<br/>{{Version/ServerSince|2.5.0}}}}
+{{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 as the Login Name is unique!<br/>The Login Name must not include more than one "\"!<br/>{{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==
-The Login knows its [[Consumer]] - but there is no need to have one. The Consumer objet groups a set of Login objects.
+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).
-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!<br/>{{Version/ServerSince|2.5.0}}}}
+{{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}})}}
 [[Category:UBIK|Login]]

← Older revision		Revision as of 14:50, 1 July 2015
Line 17:		Line 17:
	Domain Name + "\" + Name		Domain Name + "\" + Name

−	{{Attention\|The Login Object may only be saved as the Login Name is unique!}}	+	{{Attention\|The Login Object may only be saved as the Login Name is unique!<br/>{{Version/ServerSince\|2.5.0}}}}