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

Limit access to different status pages (password restricted) #1401

Closed
1 task done
mathiskir opened this issue Mar 21, 2022 · 7 comments
Closed
1 task done

Limit access to different status pages (password restricted) #1401

mathiskir opened this issue Mar 21, 2022 · 7 comments
Labels
area:status-page Everything related to the status page feature-request Request for new features to be added

Comments

@mathiskir
Copy link
Contributor

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I would like to be able to set a password for example for status page a and let status page b be public.
(Louislam just made it possible to create multiple pages)

✔️ Solution

It could be using a password or requiring login with the admin account etc.

❓ Alternatives

📝 Additional Context

@mathiskir mathiskir added the feature-request Request for new features to be added label Mar 21, 2022
@val123456
Copy link

I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-)

@mathiskir
Copy link
Contributor Author

mathiskir commented Mar 24, 2022

I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-)

its a good way but i want it to be implemented into uptime kuma

@wrench12435678
Copy link

This would be usefull or at least if you add a domain name, it only is acsessible if coming from that domain.

@SteffoSpieler
Copy link

Would be great if it would be possible to set a custom password per status page.

@CommanderStorm
Copy link
Collaborator

@mathiskir
I think this is a duplicate of #1050
If you agree please close this issue, as issue-management is harder with zombies hanging around.
If you disagree, what is the difference?

@vaemarr
Copy link

vaemarr commented Nov 22, 2023

I too would like to see this, it's one of the few things actually stopping us from using this with our clients.

@CommanderStorm
Copy link
Collaborator

@mathiskir
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #1050 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2023
@CommanderStorm CommanderStorm added the area:status-page Everything related to the status page label Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:status-page Everything related to the status page feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

6 participants