question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make it possible to change page visibility (Authenticated Vs Anonymous)

See original GitHub issue

Feature 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:

image

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:5
  • Comments:18 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
BobbyCGDcommented, Jul 21, 2020

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.

1reaction
mikebudzynskicommented, Jan 18, 2022

We’re now working on this feature. It will likely be released in preview in summer.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Site visibility in Power Pages
Learn how to secure your Power Pages site by using site visibility and switch site visibility between private and public options.
Read more >
permissions - Anonymous access to pages
I would like to give anonymous access to pages. So, for that I have given anonymous view items permission to pages list. So,...
Read more >
Control access and visibility - GitLab Docs
Only visible to authenticated users between GitLab 13.1 and GitLab 15.0. Select Save changes. For more details on project visibility, see Project visibility....
Read more >
Display different content for anonymous and logged in users
Create a display for the authenticated user view. Set the page path; Set the Access restrictions (eg., by Authenticated role) · Create a...
Read more >
How to Define Public Pages (Viewable by Anonymous Users)
To make some pages or parts of the repository visible to people without requiring them to be authenticated to the Platform, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found