Web3-Login is a decentralized OpenID Connect (OIDC) provider leveraging web3 technologies. Unlike centralized authentication systems, it offers a seamless authentication experience using your Ethereum address. No personal data or passwords required—just sign the transaction and you're authenticated!

The internet today largely relies on identity-based access rather than ownership-based access authorization. Web3-Login bridges this gap. It uses Ethereum addresses as identities and verifies the ownership of NFTs to grant access to services. In essence, it embodies the core principle of web3: decentralization.

Our inspiration stems from the realization that most online services today hinge on identities instead of actual ownership of access authorization. This paradigm shift, from identity to ownership, inspired us to create Web3-Login. The service uses Ethereum addresses as a form of identity, but it's the ownership of an NFT that grants access to the various online services.

Web3-Login revolutionizes the traditional login mechanism. Instead of usernames and passwords, it uses web3 keys (public/private key pairs) and NFTs. Developers can thus integrate a novel login functionality into their projects, allowing users to use their crypto wallets for authentication.

To get started, all you need is a Web3 wallet such as MetaMask or Coinbase. No separate username or password. Just choose your Web3 wallet from the list, and sign your transactions.

To get started with web3-login, you can follow these steps to build and run the application:

cargo build   # Build the project
cargo test    # Run tests
cargo run     # Start the web3-login service

openssl genpkey -algorithm ed25519
openssl genrsa --traditional -out private_rsa.pem 1024

Copy the generated private key to config.yml.

Cloudflare Argo Tunnel provides a secure way to connect your infrastructure to the Cloudflare network without exposing public IPs. By integrating it with the web3-login service, you can achieve improved performance and security for user authentication. It's especially beneficial for projects where identity and privacy matter.

1. Create a new tunnel for your service:

   cloudflared tunnel create oidc-web3-login

2. Move the generated JSON (your tunnel credentials) to the .cloudflared directory:

   cp changeme-e246.json .cloudflared/

3. Update the tunnel settings in your .cloudflared/config.yml:

   url: http://provider:8080
   tunnel: changeme-e246
   credentials-file: /etc/cloudflared/changeme-e246.json

With the configurations in place, you can now run the web3-login service along with Cloudflare Argo Tunnel using Docker Compose:

docker-compose up -d

If you wish to run the web3-login service without Docker Compose, you can use the following docker run command:

docker run -d -p 8080:8080 --name web3-login ghcr.io/web3-login/web3-login/web3-login:latest

Note: Ensure the configurations and required volumes are appropriately set if you're opting for this method.

Absolutely! The resilience and decentralization principle behind Web3-Login means you're not locked into relying solely on our infrastructure.

Web3-Login is constructed atop the OpenID Connect (OIDC) framework. This enables anyone to host the OIDC server on their own infrastructure. So, even if there were issues with our primary domain, you can seamlessly transition by setting up the OIDC server on a different domain and pointing your application there.

To achieve this, you would:

1. Host the OIDC server on your chosen domain or server.
2. Update your OpenID Connect client's configuration to refer to your new domain.

It's all about giving you the control. The decentralization aspect ensures that the login process remains robust and reliable, irrespective of potential disruptions to our primary service.

For a practical example, when setting up on your own domain, you'll need to replace the Authorize URI in the example config with your server's domain.