caddy-auth-portal
acme-companion
Our great sponsors
caddy-auth-portal | acme-companion | |
---|---|---|
15 | 32 | |
668 | 7,250 | |
- | 0.7% | |
9.0 | 7.6 | |
about 2 years ago | 23 days ago | |
Go | Shell | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
caddy-auth-portal
-
Any recommendations for internal network inventory website?
Caddy Auth Portal. Also has the advantage of providing unified secure 2FA.
-
Why I'm Using HTTP Basic Auth in 2022
I am very happy with the this caddy extension: https://github.com/greenpau/caddy-auth-portal.
Sorts this precise use case for me, need for common login provider. Without the banality of basic auth.
-
Authentik is the easy Single Sign On tool we all need!
After dabbling with Caddy's auth-portal, nginx Vouch proxy, Keycloak and Authelia I found Authentik.
-
Has anyone tried the auth-portal Plugin for Caddy?
I'm trying to migrate from Nginx to the simpler Caddy and am looking for an auth-request replacement. The Caddy auth-portal looks perfect, it even has local user management. I might spin it up in Docker.
-
Discussion: Which reverse proxy is the best?
Usually with this plugin: https://github.com/greenpau/caddy-auth-portal
-
Anyone with experience setting up SSO/Dashboard/Okta alternative?
Thereβs caddy-auth-portal which Iβve not used myself, but heard good things about.
-
Single Sign On (SSO) with subdomains using Caddy v2
I hope this post helps setting up your SSO with Caddy. I'd highly recommend trying it out if you find yourself always needing to authenticate with different services on your domain β and check out caddy-auth-portal's docs for even more advanced features!
-
Migrating from LastPass to Bitwarden - opinions?
This sounds like an XY Problem. It sounds like you're missing a good IAP solution to deal with access controls. Something like oauth2_proxy, Keycloak, Pomerium, etc. Hell, I've even set up a basic IAP with Caddy and Oauth Portal.
-
Minimalist LDAP and JWT issuing end-point.
Have you looked at caddy-auth-portal
acme-companion
-
Wireguard (docker-compose) has stopped being able to connect to the internet.
My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:
-
Add https to docker app
Probably want acme with nginx https://github.com/nginx-proxy/acme-companion
-
Beginner questions about deploying node.js app on Beanstalk
setting up letsencrypt with nginx-proxy and acme-companion
-
Further investigating 403 β access forbidden by rule
I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).
-
What is the correct way to have my webapp in one container and the webserver in another?
We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).
-
dockerfile for httpd
Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.
-
nginx-proxy-manager abandoned?
You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion
-
Tools for automation and daily tasks
https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus
-
Trying to figure out how to update our SSL certificates for a couple of docker webapps using nginx
If you use Docker anyway, have a look at nginx-proxy and it's acme companion. When running on the same host, it will automatically find other containers via docker.sock and then route and create Let's Encrypt certificates for the (sub-)domain you add via env.
-
Help for Iran: How to host the signal-tls-proxy for iran behind a nginx
For the signal proxy, they are using nginx and letsencrypt already and the ports 80 and 443. My current setup already involves an nginx proxy as well as a certbot, so how can I host this signal proxy in my infrastructure?
What are some alternatives?
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
authentik - The authentication glue you need.
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
Docker Compose - Define and run multi-container applications with Docker
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
caddy-security - π Authentication, Authorization, and Accounting (AAA) App and Plugin for Caddy v2. π Implements Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google, Facebook, Okta, etc.), SAML Authentication. MFA/2FA with App Authenticators and Yubico. π Authorization with JWT/PASETO tokens. π
docker-letsencrypt-nginx-proxy-companion - Automated ACME SSL certificate generation for nginx-proxy [Moved to: https://github.com/nginx-proxy/acme-companion]
dex - OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors