Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc Feedback: #7489

Open
nrcuster opened this issue Dec 13, 2023 · 0 comments
Open

Doc Feedback: #7489

nrcuster opened this issue Dec 13, 2023 · 0 comments

Comments

@nrcuster
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant