Difference between revisions of "Fusion Registry Security Overview Version 10"
(→Security Overview) |
(→Security Overview) |
||
| Line 3: | Line 3: | ||
Security in the Fusion Registry is split into two distinct functions, '''Authentication''' and '''Authorisation'''. Authentication is the process of ensuing user credentials match up against a valid user account, and then loading the user details into the session. Authorisation is the process of ensuring a user is allowed to perform the action they are trying to perform. | Security in the Fusion Registry is split into two distinct functions, '''Authentication''' and '''Authorisation'''. Authentication is the process of ensuing user credentials match up against a valid user account, and then loading the user details into the session. Authorisation is the process of ensuring a user is allowed to perform the action they are trying to perform. | ||
| − | The Fusion Registry has a single in built account for the | + | The Fusion Registry has a single in built account for the root user, this is set up on installation. |
| − | The Fusion Registry provides a number of methods for user Authentication, they are: | + | In order to support additional users, the Fusion Registry can link to an external Authentication Server, this may be [[Fusion Security]] or Microsoft Active Directory. |
| + | |||
| + | |||
| + | In Addition to the root user, additional users can log in | ||
| + | |||
| + | The Fusion Registry | ||
| + | |||
| + | provides a number of methods for user Authentication, they are: | ||
* Use the Fusion Security Web Server to Authenticate Users | * Use the Fusion Security Web Server to Authenticate Users | ||
Revision as of 08:22, 28 April 2019
Contents
Security Overview
Security in the Fusion Registry is split into two distinct functions, Authentication and Authorisation. Authentication is the process of ensuing user credentials match up against a valid user account, and then loading the user details into the session. Authorisation is the process of ensuring a user is allowed to perform the action they are trying to perform.
The Fusion Registry has a single in built account for the root user, this is set up on installation.
In order to support additional users, the Fusion Registry can link to an external Authentication Server, this may be Fusion Security or Microsoft Active Directory.
In Addition to the root user, additional users can log in
The Fusion Registry
provides a number of methods for user Authentication, they are:
- Use the Fusion Security Web Server to Authenticate Users
- Use Active Directory to Authenticate Users
- Use Certificate Authentication
The use of an external Authentication Server
