Difference between revisions of "Login"
| Line 1: | Line 1: | ||
==Basics== | ==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 | + | |
| − | A Login can be marked | + | |
==Name== | ==Name== | ||
| − | The name | + | The name of the Login object. |
| − | {{Attention|The name of a Login | + | {{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 | + | {{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 "\" | + | |
==Login Name== | ==Login Name== | ||
| − | Unique | + | Unique identifier of a Login object. The default value is: '''Domain Name + "\" + Name''' |
| − | The | + | |
| − | Domain Name + "\" + Name | + | |
| − | {{Hint|If you enter a value matching this pattern, the domain name and name of the | + | {{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 | + | {{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== | ||
| − | It is possible to set a password for a Login. Whenever a connection to UBIK is established, the | + | 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== | ==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 | + | {{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 11:04, 20 October 2015
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.
Name
The name of the Login object.
Domain Name
The domain name is used to group Logins, where the name of Logins must be unique within one domain.
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).
