Jump to: navigation, search

Difference between revisions of "Login"


m
Line 3: Line 3:
 
==Name==
 
==Name==
 
The name of the Login object.
 
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==
 
==Domain Name==
 
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, 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==
 
==Login Name==
 
Unique identifier of a Login object. The default value is: '''Domain Name + "\" + 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==
 
==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).
 
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]]
 
[[Category:UBIK|Login]]

Revision as of 15:18, 2 May 2016

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.

IC Attention.pngThe 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.

IC Attention.pngThe domain name of a Login Object must not include a "\".

Login Name

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

IC Hint square.pngIf you enter a value matching this pattern, the domain name and name of the Login are set automtically!
IC Attention.pngThe 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).

IC Hint square.pngIf you want to use the multi-tenancy feature, you must link the Login to a Consumer belonging to a tenant!