Security Configuration - Overview - Revision history

Vmurrell: /* Authorisation - Version 11 */

2025-11-03T11:58:48Z

‎Authorisation - Version 11

Vmurrell: /* Authorisation - Version 10 */

2025-11-03T11:58:31Z

‎Authorisation - Version 10

Vmurrell: /* Authentication */

2025-11-03T11:57:03Z

‎Authentication

Vmurrell at 16:39, 30 October 2025

2025-10-30T16:39:26Z

Vmurrell: /* Restrict Access */

2024-09-12T15:17:16Z

‎Restrict Access

Vmurrell: /* Worksheet Passwords */

2024-09-12T15:16:58Z

‎Worksheet Passwords

Vmurrell: /* Root User */

2024-09-12T15:16:40Z

‎Root User

Vmurrell: /* Authorisation - Version 10 */

2024-09-12T15:16:26Z

‎Authorisation - Version 10

Vmurrell: /* Fusion Security (not supported in Version 11 onwards) */

2024-09-12T15:16:05Z

‎Fusion Security (not supported in Version 11 onwards)

Vmurrell: Vmurrell moved page Security Configuration to Security Configuration - Overview

2024-09-12T14:48:57Z

Vmurrell moved page Security Configuration to Security Configuration - Overview

@@ Line 28: / Line 28: @@
 The Registry uses the Group information from the Authentication service as described [[https://wiki.sdmxcloud.org/Fusion_Security_Manager_(FR_V11)#Security_Groups| here. ]]
-== Authorisation - Version 11 ==
+== Authorisation ==
 This is handled in [[Fusion_Security_Manager_(FR_V11) |Fusion Security Manager. Please follow the link to read more.]]

← Older revision		Revision as of 11:58, 3 November 2025
Line 27:		Line 27:

	The Registry uses the Group information from the Authentication service as described [[https://wiki.sdmxcloud.org/Fusion_Security_Manager_(FR_V11)#Security_Groups\| here. ]]		The Registry uses the Group information from the Authentication service as described [[https://wiki.sdmxcloud.org/Fusion_Security_Manager_(FR_V11)#Security_Groups\| here. ]]
−
−	~~== Authorisation - Version 10 ==~~
−	To understand Authorisation, it is important to understand the security model for the Fusion Registry. Each user account links to zero or more [[Organisations]] maintained in the Fusion Registry. The Organisation a user account can be linked to falls into one of three categories:
−	~~# An Agency~~
−	~~# A Data Provider~~
−	~~# 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.~~
−
−	~~A '''Agency''' user is able to create, maintain, and delete structures that belong to the Agency, or any of its sub-agencies.~~
−
−	~~A '''Data Provider''' user is able to validate and convert datasets the Data Provider has been set up to provide data for via a [[Provision Agreement]].~~
−
−	~~A '''Data Consumer''' user has no special privileges provided by default, however they are able to access the Registry if the product has been set up to enforce login.~~

	== Authorisation - Version 11 ==		== Authorisation - Version 11 ==

← Older revision		Revision as of 11:57, 3 November 2025
Line 26:		Line 26:
	After the Authentication process, the Registry must Authorise the user to access the resources. This is achieved by the Registry linking the user's account to one or more [[Organisations]], this link is achieved in different ways depending on the Authentication mechanism. You can learn more about how this works [[How_Registry_Interfaces_With_Active_Directory \|in this article.]]		After the Authentication process, the Registry must Authorise the user to access the resources. This is achieved by the Registry linking the user's account to one or more [[Organisations]], this link is achieved in different ways depending on the Authentication mechanism. You can learn more about how this works [[How_Registry_Interfaces_With_Active_Directory \|in this article.]]

−	~~=== Fusion Security (not supported in Version 11 onwards) ===~~
−	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 Registry, including which [[Organisations]] the user belongs to. No additional configuration is required in the Registry.
−
−	~~Fusion Security is only applicable for Fusion Registry 10 and is not an option for Fusion Registry version 11.~~
−
−	~~=== Active Directory ===~~
−	~~'''Version 10'''~~
−
−	~~If Active Directory is used as an Authentication server, then the Common Name (CN) is used to authenticate with the server.~~
−
−	~~'''Version 11'''~~
	The Registry uses the Group information from the Authentication service as described [[https://wiki.sdmxcloud.org/Fusion_Security_Manager_(FR_V11)#Security_Groups\| here. ]]		The Registry uses the Group information from the Authentication service as described [[https://wiki.sdmxcloud.org/Fusion_Security_Manager_(FR_V11)#Security_Groups\| here. ]]

@@ Line 1: / Line 1: @@
 [[Category:RegistrySecurity]]
-[[Category:Fusion Registry Install]]
+[[Category:Fusion Registry Configuration]]
 ==Overview==

@@ Line 65: / Line 65: @@
 ===Restrict Access===
-Fusion Metadata Registry's default security ensures that generating an Excel workbook from a Report Template is a restricted action. Only users with certain access permission can generate an Excel workbook. The rules are:
+Fusion Registry's default security ensures that generating an Excel workbook from a Report Template is a restricted action. Only users with certain access permission can generate an Excel workbook. The rules are:
 {| class="wikitable"

@@ Line 86: / Line 86: @@
 ===Worksheet Passwords===
-When a password is applied, when Fusion Metadata Registry generates an Excel workbook from a Report Template definition, it will ensure non-observation cells are locked and can not be edited unless a password is supplied to unlock the worksheet.
+When a password is applied, when Fusion Registry generates an Excel workbook from a Report Template definition, it will ensure non-observation cells are locked and can not be edited unless a password is supplied to unlock the worksheet.
 This will help prevent the data reporter editing the workbook in such a way to make it unreadable by the Registry.

@@ Line 60: / Line 60: @@
 The Registry provides a single root user account, where the credentials are stored locally (not in an external authentication service).  The Registry authenticates the root user, and as such the root user is always able to log into the product should the external authentication service become inaccessible.
-It is not a requirement to set up an external authentication service - Fusion Metadata Registry can be run in ''single user mode'' using the built-in '''root''' superuser account.  Root user has unrestricted access to the product, and as such security rules do not apply to the root user.
+It is not a requirement to set up an external authentication service - Fusion Registry can be run in ''single user mode'' using the built-in '''root''' superuser account.  Root user has unrestricted access to the product, and as such security rules do not apply to the root user.
 ==Reporting Template==

@@ Line 40: / Line 40: @@
 == Authorisation - Version 10 ==
-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:
+To understand Authorisation, it is important to understand the security model for the Fusion Registry.  Each user account links to zero or more [[Organisations]] maintained in the Fusion Registry.  The Organisation a user account can be linked to falls into one of three categories:
 # An Agency
 # A Data Provider

@@ Line 27: / Line 27: @@
 === Fusion Security (not supported in Version 11 onwards) ===
-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 Registry.
+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 Registry, including which [[Organisations]] the user belongs to.  No additional configuration is required in the Registry.
 Fusion Security is only applicable for Fusion Registry 10 and is not an option for Fusion  Registry version 11.

← Older revision	Revision as of 14:48, 12 September 2024
(No difference)