MOSIP Docs
LTS
LTS
  • Home
  • Overview
  • ID Lifecycle Management
    • ID Schema
    • Identifiers
  • ID Authentication
  • Privacy and Security
    • Data Protection
    • Keys
    • Privacy
  • Biometrics
    • ABIS
    • ABIS API
    • Biometric SDK
    • Biometric Devices
    • SBI
    • Biometric Image Specification
    • FTM
  • Partners
  • Modules
    • Pre-registration
      • Pre-registration User Guide
    • Registration Processor
    • Registration Client
      • Operator Onboarding
      • Registration Client User Guide
      • Registration Client Home Page
      • Registration Client Configuration
      • Registration Client UI Spec
    • Commons
    • ID Repository
    • Partner Management
    • Data Share
    • Packet Manager
    • WebSub
    • Resident Services
    • Administration
      • Admin Portal User Guide
    • ID Authentication Services
    • Reporting
    • Automation Testing
    • Storage
  • Deployment
    • Sandbox Deployment
    • Server Hardware Requirements
    • Country Implementation
    • Masterdata Guide
  • APIs
  • Community
    • Contributions
    • Code of Conduct
  • License
Powered by GitBook
On this page
  • Overview
  • WebSub in MOSIP

Was this helpful?

  1. Modules

WebSub

PreviousPacket ManagerNextResident Services

Last updated 3 years ago

Was this helpful?

Overview

WebSub provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content to subscribers when it becomes available. WebSub was previously known as PubSubHubbub. See .

WebSub in MOSIP

In MOSIP WebSub is used to share data with services and partners. message broker has been used to implement the WebSub APIs. Message brokers are a natural fit for the implementation of WebSub hubs as they serve a similar purpose.

Refer for further details.

WebSub repo
W3C WebSub
Kafka