You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This documentation on How to Restrict DevPortal visibility by Role is incomplete. The step that is missing is after selecting the option "Restrict by role(s)" is how to then enter the Role(s) to which you want to restrict the devportal viewing.
I have found after some experimentation that for the "Roles" you enter, there are certain specific requirements which must be met and should be included in this documentation.
First, you must place the cursor into the "Roles" box before seeing the instructions (grayed in the background) to "Enter roles and press Enter". Next, you must enter the domain and the role name exactly as they appear in the list of Roles for a given domain in one of the Primary and/or any Secondary Userstores. This means that the user entering the Role restrictions must have privileged access and/or knowledge of the role information needed to enter this restriction. Otherwise, the entry will be considered invalid, which is indicated by a rolename in Red. Valid domain/rolenames entered in the Roles block will be shown with a gray background.
The text was updated successfully, but these errors were encountered:
Location : https://apim.docs.wso2.com/en/4.1.0/design/advanced-topics/control-api-visibility-and-subscription-availability-in-developer-portal/
This documentation on How to Restrict DevPortal visibility by Role is incomplete. The step that is missing is after selecting the option "Restrict by role(s)" is how to then enter the Role(s) to which you want to restrict the devportal viewing.
I have found after some experimentation that for the "Roles" you enter, there are certain specific requirements which must be met and should be included in this documentation.
First, you must place the cursor into the "Roles" box before seeing the instructions (grayed in the background) to "Enter roles and press Enter". Next, you must enter the domain and the role name exactly as they appear in the list of Roles for a given domain in one of the Primary and/or any Secondary Userstores. This means that the user entering the Role restrictions must have privileged access and/or knowledge of the role information needed to enter this restriction. Otherwise, the entry will be considered invalid, which is indicated by a rolename in Red. Valid domain/rolenames entered in the Roles block will be shown with a gray background.
The text was updated successfully, but these errors were encountered: