Make it possible to change page visibility (Authenticated Vs Anonymous)
See original GitHub issueFeature request
The fact that it is possible to change the visibility of the buttons according to the user status is great (authenticated vs anonymous or both). However, I don’t see why it is limited to buttons? How come you can’t specify if a user has to be logged in to see a particular page or not?
Example:
Let’s say we want to hide the APIs List page from users who are not signed in, and redirect them to the Sign in/Sign up page if they visit said page. After which they get redirected back to where they started, which is the APIs List page.
This is important because, let’s suppose we want to share one of the APIs with a client who’s interested in trying it out. What you would usually do is send them a link similar to the following:
https://developers.createitreal.com/sandbox#api=wsopenapi
In the case where the client is not signed in, he will be redirected to the Sign in page to sign in, once he does so, he gets redirected back to the page he was trying to visit in the first place.
It would be great if that would be possible even in the case where the client doesn’t have account, signs up and get redirected back to the page where he started. But I’m aware it’s not going to be easy.
Implementation suggesstion
It would be interestitng to add a visibility field here for each page:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:18 (7 by maintainers)
Top GitHub Comments
I work for a large organisation which relies on the APIM Portal to create an ecosystem for users. As such we are adding more and more content to our portal every day. We quickly faced the same issue and would love to hear some ideas on how we should go about restricting access to pages for unauthenticated users for the moment until this becomes available through the portal.
We’re now working on this feature. It will likely be released in preview in summer.