luds
oauth2-proxy
luds | oauth2-proxy | |
---|---|---|
25 | 98 | |
571 | 8,712 | |
1.1% | 2.1% | |
6.7 | 9.0 | |
3 months ago | 1 day ago | |
Makefile | Go | |
- | 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.
luds
-
"I am so stupid I cant do webdev (auth part)" rant
If it is really only about auth maybe consider https://github.com/lnurl/luds/blob/luds/04.md LNURL Auth. But then your users should be able to understand the idea of private/public keys.
-
Bitcoin's Lightning Network Getting a Privacy Upgrade
Independent solutions have also sprung up – notably, lnproxy, an invoice privacy tool (invoices are simply payment requests), and LNURL, a suite of tools for enabling communication between various Lightning applications and services over the web. So what’s a privacy-focused Bitcoiner to do, rely on the fledgling BOLT 12 specification or turn to one of these independent tools?
-
Logging into a website using Lightning authentication (lnurl-auth app 'GetIn'). No more usernames or passwords, blazing fast and effortless login. I love it.
The technical specification is here: https://github.com/lnurl/luds/blob/luds/04.md
- Lightning login app - good or bad idea?
-
Setting up a non time restricted Lightning invoice (QR-Code)
Thanks! yes, managed to set the static QR-code up via the LNURLp extension. How can I figure out if a wallet supports LNURL? I just tried sending myself via BlueWallet and it worked :) I've found this article saying "...it's been adopted in some of the most popular Lightning wallets including Zap, Phoenix, Breez, Blue Wallet and Wallet of Satoshi, as well as dozens of other apps." - not sure how to interpret the table in Github though.
-
Next.js - tRPC - LN App starter, modern full stack Lightning Network App starter
Since the inception of the lightning network and the development of the ln-url standard, the holy grail of "bank as a web app" is not only a reality but only 5 minutes of set up time and about 30$ of hosting costs away. This starter implements such an app. Authentication and Users are already there, and basic in- and out flow of purchasing power is taken care of. Users can authenticate themselves, deposit and withdraw up to 1000 sats. Whatever happens in between is up to the developer.
-
Recurring Bitcoin lightning payments are coming! What are the best applications?
Could have been an LNURL payRequest. Unfortunately that does require a service provider, as someone has to be running a server to service the URL. You can host that yourself, of course, but that's way more complex than 99% of Lightning users will tolerate. Many will accept the risks of delegating the hosting out to a third party.
-
Spending Bitcoin at Costa Coffee Gibraltar - Possibly the 1st global franchise to accept Bitcoin physically in Europe
There is a nice article that describes how this feature works on the NFC chip. The URL it produces uses LUD03 and LUD17 from the LNURL spec. This diagram (source) also nicely explains how it works. In this case, the 'User with a smartphone' would be the merchant's point-of-sale device, and the web application would be the LNURL-withdraw server.
- List of Apps & Wallets That Let You Log In With Lightning ⚡️
-
Danny Scott ⚡ on Twitter : Announcing “The Bolt Card”
And here's specification: https://github.com/fiatjaf/lnurl-rfc
oauth2-proxy
-
Keycloak SSO with Docker Compose and Nginx
Recently I looked into having a relatively simple SSO setup for my homelab. My main objective is that I could easily login with Google or GitHub auth. At my previous job I used both JetBrains Hub [1] and Keycloak but I found both of them a bit of a PITA to setup.
JetBrains Hub was really, really easy to get going. As was my previous experience with them. The only thing that annoyed me was the lack of a latest tag on their Docker registry. Don't get me wrong, pinned versions are great, but for my personal use I mostly just want to update all my Docker containers in one go.
On the other hand I found Keycloak very cumbersome to get going. It was pretty easy in dev mode, but I stumbled to get it going in production. AFAIK it had something to do with the wildcard Let's Encrypt cert that I tried to use. But after a couple of hours, I just gave up.
I finally went with Dex [2]. I had previously put it off because of the lack of documentation, but in the end it was extremely easy to setup. It just required some basic YAML, a SQLite database and a (sub)domain. I combined Dex with the excellent OAuth2 Proxy and a custom Nginx (Proxy Manager) template for an easy two line SSO configuration on all of my internal services.
In addition to this setup, I also added Cloudflare Access and WAF outside of my home to add some security. I only want to add some CrowdSec to get a little more insights.
1. https://www.jetbrains.com/hub/
2. https://dexidp.io/
3. https://github.com/oauth2-proxy/oauth2-proxy
3. https://github.com/alex3305/unraid-docker-templates
-
Multi client authentication with auth0 and oauth2-proxy
Authentication providers like Auth0 and Okta have become commonplace in software development. These providers help take this work off of your plate, and this can be made even easier by using a reverse proxy that provides authentication capabilities, like oauth2-proxy.
-
Why You Should Migrate to OAuth 2.0 From API Keys
There's also other problems you might run into when using JWT: - First using scopes for permissions like Slack does can generate a token so large that a server might refuse it (One of many examples: https://github.com/oauth2-proxy/oauth2-proxy/issues/644, any rational server won't allow unlimited sized header), in my company they did this with the convention of read:team:product:resource but if you're an admin and have every rights by default, then you can't use the generated token by default as it will be too large. I think Quarkus works that way and you might encounter some problems with you don't configure it correctly. - Second is that it will cost a lot of bandwidth to send this header each time you're doing something, and probably won't be the perfect answer for what you want to do (do you really have third parties calling your API ?) - Third is about security concerns, you might say that having your permissions in a token is not as bad as you might think but in case of a Man In The Middle attack, you could leak information about your company, process or business intelligence that could have been prevented. - Fourth and that'll be the last, is that you can't revoke a JWT. And if you say you can, then you don't need a JWT at the first time because it would defeat the principle of a self contained JWT.
-
Moving from Google workspace to Microsoft 365 and implementing Zero Trust
That is not how you do Zero Trust. You want to use an Identity Aware Proxy. There are lots of ways you can implement this with Google as your core auth. For example Pomerium or oauth2-proxy.
-
Microsoft launches Windows App for accessing PCs in the cloud from any device
I use self-hosted Apache Guacamole (RDP) through a reverse proxy with Google SSO (oauth2-proxy[0]). So easy to access my desktop from virtually any browser (mobile isn't the best though). This would be a good solution for gaming, but for other activities RDP is unbeatable imo.
[0] https://github.com/oauth2-proxy/oauth2-proxy
-
Best Practice For Serving Static (Frontend) Files with NGINX in K8s?
Meet https://oauth2-proxy.github.io/oauth2-proxy/ It could be deployed in the cluster somewhere and reuse it where needed. We do this to authenticate prometheus,alertmanager ui for useres
-
Any thoughts on implemented access control of self hosted front end apps?
At work, I've used oauth2-proxy as a sidecar container (on Kubernetes) for an app that has no authentication mechanism. Pretty straightforward, works well. I think this or Authelia is your best bet.
-
Authentik reverse proxy vs swag
BTW also keycloak and other similar products offer the oauth-proxy capability, I even used the original oauth2-proxy https://github.com/oauth2-proxy/oauth2-proxy for a while, but it was getting too difficult to maintain for me. I used for a while https://github.com/thomseddon/traefik-forward-auth that was a smart hack configuring a single upstream provider, but it look abandoned. So I was considering authentik but apparently it's just oauth2-proxy embedded in it, at that point why not use oauth2-proxy directly.
-
How to build Auth in 2023 with go?
Like auth basic? Mate, its 2023 get that RestAPI endpoint behind an OAuth proxy. github.com/oauth2-proxy/oauth2-proxy is a good one on a budget or use some cloud provider's ApiGateway and IAM services.
-
Pomerium or Authentik?
I use it in combination with oauth2-proxy, which sits in front of my network and the various services I host. https://github.com/oauth2-proxy/oauth2-proxy
What are some alternatives?
BlueWallet - Bitcoin wallet for iOS & Android. Built with React Native
traefik-forward-auth - Minimal forward authentication service that provides Google/OpenID oauth based login and authentication for the traefik reverse proxy
lightning-address - Lightning Address - like an email address, but for your Bitcoin
vouch-proxy - an SSO and OAuth / OIDC login solution for Nginx using the auth_request module
apollo - Muun Android wallet
authelia - The Single Sign-On Multi-Factor portal for web apps
satdress - Federated Lightning addresses server.
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
developer-guide - Github mirror of our developer documentation at https://docs.siasky.net/
Docusaurus - Easy to maintain open source documentation websites.
lnbits-legend - LNbits, free and open-source lightning-network wallet/accounts system. [Moved to: https://github.com/lnbits/lnbits]
caddy-auth-portal - Authentication Plugin for Caddy v2 implementing Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google, Facebook, Okta, etc.), SAML Authentication. MFA with App Authenticators and Yubico.