Skip to main content

Secure centralized authentication SDK for FastAPI microservices

Project description

🔐 Verge Auth SDK Secure Identity & Access Management for FastAPI Microservices

Verge Auth SDK is a lightweight integration library that connects your FastAPI microservices to the Verge Auth Platform — a centralized identity, role management, and access-control system built for modern SaaS applications.

With a single line of code, your service is fully protected and becomes part of a unified authentication ecosystem:

from verge_auth_sdk import add_central_auth add_central_auth(app)

🚀 What Verge Auth Provides

✓ Centralized Login

Your users authenticate through the Verge Auth hosted login experience.

✓ Role-Based Access Control (RBAC)

Create roles inside the Verge Auth Dashboard and assign access to microservices and their granular operations.

✓ Route-Level Permissions

When a service integrates the SDK, its available routes automatically appear in the Verge Auth dashboard for permissions assignment.

✓ Group & User Management

Assign roles to users or user groups for highly flexible access control.

✓ Secure Communication

All microservice-to-auth communication is secured using service credentials provided during onboarding.

🧭 End-to-End User Flow

  1. Account Creation

Users sign up with their organization details, company domain, and email.

  1. Email Verification

A verification link is sent from no-reply@vergeinfosoft.com . Once verified, the user is redirected to the Verge Auth platform.

  1. Login

Users can sign in through the “Verge IAM” login page using their verified email and password.

  1. Auth Dashboard

Once logged in, the dashboard displays:

Total users

Active groups

Available roles

Audit logs

Permissions overview

🎛 Role-Based Access Control (RBAC)

RBAC inside Verge Auth is designed to be extremely intuitive — while supporting enterprise-level control.

Creating a Role

Inside the Roles section:

Click New Role

Enter the role name (e.g., HR Manager, Operations Admin)

Optional: Add a description

Select the Service you want this role to access

Example: employees-service, billing-service, appointments-service

After selecting a service, the system automatically shows all available routes for that service

Example:

/employees/

/employees/{id}

/employees/create

/employees/update

/employees/delete

Each route is presented with clear CRUD permissions:

Create

Read

Update

Delete

You can either:

Grant Full Access to that service

OR choose granular permissions route-by-route

Save the role

It instantly becomes available for assignment

Role creation modal with a dropdown for service selection and an auto-generated route list for CRUD assignment.

🧑‍🤝‍🧑 Assigning Roles to Users or Groups

After creating a role, you can:

Assign to a User

Go to Manage Users

Edit a user

Select one or more roles

Save changes

Assign to a User Group

Create a group (e.g., HR Team, Finance Department)

Assign roles to the group

Add users into the group (they automatically inherit the group’s permissions)

This makes onboarding smoother and keeps role management scalable.

🔌 Integrating the SDK Into a Microservice Install from PyPI pip install verge_auth_sdk

Add the Middleware from fastapi import FastAPI from verge_auth_sdk import add_central_auth

app = FastAPI() add_central_auth(app)

That’s it. The service will now:

✓ Authenticate incoming requests ✓ Communicate securely with Verge Auth ✓ Provide user identity + roles ✓ Automatically register its routes for RBAC assignment

⚙ Environment Configuration

Each service requires a minimal set of environment variables:

######################################################################

AUTH_INTROSPECT_URL= AUTH_LOGIN_URL=

VERGE_CLIENT_ID= VERGE_CLIENT_SECRET=

VERGE_SERVICE_SECRET=

These are provided by Verge Infosoft during onboarding.

Optional secret provider:

SECRETS_PROVIDER=env # azure | aws

########################################################################

🛡 Middleware Responsibilities

The SDK transparently handles:

User authentication

Role injection

Cookie vs header auth

Unauthorized access responses

Service-level authentication

Route registration

You do not need to implement any auth or RBAC logic manually.

🔐 Security Highlights

RSA-based JWT verification

Centralized session & token lifecycle management

Strong encryption for service credentials

Multi-layer permission checks (Role → Service → Route → Operation)

HTTPS-only communication

Support for cloud key vaults

💼 Ideal For

HRMS, ERP, CRM, Billing platforms

Multi-tenant SaaS applications

Modern microservice architectures

Secure admin dashboards

Enterprise platforms needing consistent access control

🆘 Support & Onboarding

For enterprise onboarding, custom integrations, or troubleshooting:

🌐 Website https://www.vergeinfosoft.com

📧 Email contactus@vergeinfosoft.com

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

verge_auth_sdk-0.1.20.tar.gz (9.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

verge_auth_sdk-0.1.20-py3-none-any.whl (8.7 kB view details)

Uploaded Python 3

File details

Details for the file verge_auth_sdk-0.1.20.tar.gz.

File metadata

  • Download URL: verge_auth_sdk-0.1.20.tar.gz
  • Upload date:
  • Size: 9.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.11.0

File hashes

Hashes for verge_auth_sdk-0.1.20.tar.gz
Algorithm Hash digest
SHA256 825a2a2f9f982d5cfc7694e216d160eed3432feb0db3edce3d752640ec20e485
MD5 95a31b44207aa4a09d3383e109c9bc1b
BLAKE2b-256 ef04957329d5383f844faf00fb780642c768e298a192266607a0896ed6f32b99

See more details on using hashes here.

File details

Details for the file verge_auth_sdk-0.1.20-py3-none-any.whl.

File metadata

File hashes

Hashes for verge_auth_sdk-0.1.20-py3-none-any.whl
Algorithm Hash digest
SHA256 58a36c7e39371a0ec285bdbbe23502582ba13c389cad8e0d0339d8b4c0a69d1a
MD5 63dded38089dcd1fe27e5bf551109a8f
BLAKE2b-256 4c9cbcd1a14d4ea4d23eb7c10ab415e4c8b9dd7a51b350e2f14f75548e444d70

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page