One of our clients recently had a unique use case. They had a Wiki site where they wanted to restrict viewing of posts to only their app’s authorized users office teams downloaden. Picture something like a SaaS app where the Wiki site had proprietary content that our client only wanted paying users to access.
The two obvious options to implement this would be:
- Create a Wiki user for each authorized user – this has the downside that we’d need to maintain two accounts, figure out how to keep users logged into both, and deal with synchronizing account data herunterladen.
- Modify the Wiki’s application code to authorize the users in some fashion – this is problematic because it would make upgrading the Wiki software difficult gratis office software downloaden.
Turns out there’s a third option which is much smoother! Nginx has a directive called auth_request which allows nginx to authorize access to a resource based on a 2nd HTTP request spiele zumen.
The way it works is:
- Your SaaS app is setup at platform.setfive.com where users are authenticated by a Symfony application.
- You configure your Symfony application to send a cookie back with a wildcard domain of “.setfive.com”
- Your wiki is running at wiki.setfive.com and configured to authorize requests to platform.setfive.com/is-authenticated
- Now, when users request wiki.setfive.com their browser will send your Symfony authentication cookie, nginx will make a request to platform.setfive.com/is-authenticated, and if they’re authenticated they’ll be granted access to your wiki the boot film for free.
The nginx config for this is pretty straightforward as well. One thing to note is this module is not standard so on Ubuntu you do need to install the nginx-extras package to enable it excel free full chip.
Posted In: Tips n' Tricks