Data Consumer Access - Revision history

Vmurrell at 10:19, 6 October 2025

2025-10-06T10:19:04Z

Vmurrell at 13:18, 12 September 2024

2024-09-12T13:18:55Z

Vmurrell at 11:22, 10 September 2023

2023-09-10T11:22:34Z

Vmurrell at 12:27, 8 August 2023

2023-08-08T12:27:19Z

Vmurrell at 14:44, 6 March 2021

2021-03-06T14:44:53Z

Vmurrell: Created page with "Category:RegistrySecurity If a user logs into the Registry as a Data Consumer when the Registry is not enforcing login, the user will experience no differences as to an un..."

2021-03-06T14:35:30Z

Created page with "Category:RegistrySecurity If a user logs into the Registry as a Data Consumer when the Registry is not enforcing login, the user will experience no differences as to an un..."

New page

[[Category:RegistrySecurity]]
If a user logs into the Registry as a Data Consumer when the Registry is not enforcing login, the user will experience no differences as to an unauthorised user.

For a Registry with Enforce Login enabled, a Data Consumer has the ability to query the public SDMX web service. A Data Consumer may not access the Registry via the Registry User Interface and attempting to log in to the Registry will inform the user of this.

Permissions can be applied to a Data Consumer from the Security Settings page “Data Consumer Dataset Access”.

This page allows for individual Data Consumers to be assigned permission to view one or more Dataflows.

← Older revision		Revision as of 10:19, 6 October 2025
Line 1:		Line 1:
−	[[Category:~~RegistrySecurity~~]]	+	[[Category:RetiredFunctionality]]
	'''This feature is not available in Version 11.'''		'''This feature is not available in Version 11.'''

@@ Line 1: / Line 1: @@
 [[Category:RegistrySecurity]]
-This feature is not available in Version 11.
+'''This feature is not available in Version 11.'''
 If a user logs into the Registry as a Data Consumer when the Registry is not [[Server_Security|Enforcing Login]] the user will experience no differences as to an unauthorised user.

@@ Line 1: / Line 1: @@
 [[Category:RegistrySecurity]]
 This feature is not available in Version 11.
 If a user logs into the Registry as a Data Consumer when the Registry is not [[Server_Security|Enforcing Login]] the user will experience no differences as to an unauthorised user.

← Older revision		Revision as of 12:27, 8 August 2023
Line 1:		Line 1:
	[[Category:RegistrySecurity]]		[[Category:RegistrySecurity]]
		+	This feature is not available in Version 11.
	If a user logs into the Registry as a Data Consumer when the Registry is not [[Server_Security\|Enforcing Login]] the user will experience no differences as to an unauthorised user.		If a user logs into the Registry as a Data Consumer when the Registry is not [[Server_Security\|Enforcing Login]] the user will experience no differences as to an unauthorised user.

@@ Line 1: / Line 1: @@
 [[Category:RegistrySecurity]]
-If a user logs into the Registry as a Data Consumer when the Registry is not enforcing login, the user will experience no differences as to an unauthorised user.
+If a user logs into the Registry as a Data Consumer when the Registry is not [[Server_Security|Enforcing Login]] the user will experience no differences as to an unauthorised user.
 For a Registry with Enforce Login enabled, a Data Consumer has the ability to query the public SDMX web service. A Data Consumer may not access the Registry via the Registry User Interface and attempting to log in to the Registry will inform the user of this.
-Permissions can be applied to a Data Consumer from the Security Settings page “Data Consumer Dataset Access”.
+Permissions can be applied to a Data Consumer from the Security Settings page.
+This page allows for individual Data Consumers to be assigned permission to view one or more Dataflows, as shown in the example above.