Security Configuration - Revision history

Plazarou: /* Active Directory */

2024-05-10T14:26:32Z

‎Active Directory

2024-05-10T14:26:04Z

‎Active Directory

2024-05-10T10:51:48Z

‎Fusion Security

2024-05-10T10:49:38Z

‎Overview

2024-04-17T15:29:02Z

2024-03-23T12:18:49Z

2024-03-22T08:31:09Z

2023-07-19T12:00:11Z

‎Overview

2023-07-19T11:56:51Z

‎Overview

2022-08-25T14:03:57Z

‎Authorisation

@@ Line 31: / Line 31: @@
 === Active Directory ===
-For detail on setting up Active Directory, please refer to [[Authentication_Service |this article]].
+For detail on the various settings in FMR for Active Directory, please refer to [[Authentication_Service |this article]].
 If Active Directory is used as an Authentication server, then the Common Name (CN) is used to authenticate with the server.  The CN is mapped in the Fusion Metadata Registry to one or more [[Organisations]]. To learn more about how to map users to Active Directory, [[Active_Directory_-_Role_Mapping | please refer to this article]].

@@ Line 31: / Line 31: @@
 === Active Directory ===
-If Active Directory is used as an Authentication server, then the Common Name (CN) is used to authenticate with the server.  The CN is mapped in the Fusion Metadata Registry to one or more [[Organisations]]. To learn more about how to map users to Active Directory, [https://fmrwiki.sdmxcloud.org/Active_Directory_-_Role_Mapping please refer to this article.]
+For detail on setting up Active Directory, please refer to [[Authentication_Service |this article]].
 == Authorisation ==

@@ Line 29: / Line 29: @@
 === Fusion Security ===
 If the Authentication Service is Fusion Security, then the Fusion Security server will verify the user credentials and return the user account details to the Fusion Metadata Registry, including which [[Organisations]] the user belongs to.  No additional configuration is required in the Fusion Metadata Registry.
 === Active Directory ===

@@ Line 10: / Line 10: @@
 The Fusion Metadata Registry only provides Authentication services for one user; the Fusion Metadata Registry Root user.  Authentication for other users are provided by either:
-* Fusion Security Web Server
+* Fusion Security web application
 * [https://en.wikipedia.org/wiki/Active_Directory Active Directory] using the [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] protocol
 * [https://en.wikipedia.org/wiki/OpenLDAP OpenLDAP]

← Older revision		Revision as of 15:29, 17 April 2024
Line 1:		Line 1:
−	[[Category:~~Draft_-_Installation_and_Configuration~~]]	+	[[Category:Installation_and_Configuration]]

	[[Category:FMR Configuration Reference]]		[[Category:FMR Configuration Reference]]

← Older revision		Revision as of 12:18, 23 March 2024
Line 1:		Line 1:
		+	[[Category:Draft_-_Installation_and_Configuration]]
		+
	[[Category:FMR Configuration Reference]]		[[Category:FMR Configuration Reference]]
	==Overview==		==Overview==

@@ Line 9: / Line 9: @@
 * Fusion Security Web Server (up to FMR 10)
-* [[Active Directory]] using the [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] protocol
+* [https://en.wikipedia.org/wiki/Active_Directory Active Directory] using the [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] protocol
-* OpenLDAP
+* [https://en.wikipedia.org/wiki/OpenLDAP OpenLDAP]
 Once a user is Authenticated, the relevant User Account is loaded into the session, and the Registry uses its security model and rules to '''authorise''' the user is allowed to access the resource. The example below shown as example for Active Directory. You can read more [[Active_Directory_-_Set_up_Role_Mappings| about Active Directory in this article]].

@@ Line 35: / Line 35: @@
 == Authorisation ==
 To understand Authorisation, it is important to understand the security model for the Fusion Metadata Registry.  Each user account links to zero or more [[Organisations]] maintained in the Fusion Metadata Registry.  The Organisation a user account can be linked to falls into one of three categories:
-# An [[Agency]]
+# An Agency
-# A [[Data Provider]]
+# A Data Provider
-# A [[Data Consumer]]
+# A Data Consumer
 A user account may have '''administrative''' privileges, which allows the user unrestricted access to any information in the product, including access to the configuration settings of the product.