Signet
GitHubCommunityWhat's NewChatBot
  • 🌐eSignet
  • 🔍Overview
    • ✨Features
      • Signup Portal
    • âš–ī¸Principles
    • 📏Standards & Security
    • 📜License
  • đŸ’ģDevelop
    • đŸĻžTechnology
      • đŸ“ĻTechnology Stack
      • âš™ī¸Components - eSignet
      • đŸ¤ŗComponents - Signup Portal
      • 📲API
    • âš™ī¸Configure eSignet
      • ACR
      • Claims
      • .well-known
        • jwks.json
        • oauth-configuration
        • openid-configuration
  • 🎮Test
    • đŸ•šī¸Try It Out
      • Using Mock Data
      • Register Yourself
      • Integrate with eSignet
    • 👨‍đŸ’ģEnd User Guide
      • Health Portal
        • Login with Biometrics
        • Login with Password
        • Login with OTP
        • Login with QR code (Inji)
        • Knowledge Based Identification
        • Signup and Login with OTP for Verified Claims
    • 🧩Integration Guides - eSignet
      • Authenticator Plugin
      • Key Binder Plugin
      • Audit Plugin
      • Digital Wallet
        • Credential Holder
        • Wallet Authenticator
      • Relying Party
    • 🔐Integration Guide - Signup Portal
      • Identity Verifier Plugin
      • Profile Registry Plugin
      • Integration with eSignet portal
  • đŸ› ī¸Deploy
    • â›´ī¸Deployment Architecture
      • On-Prem Installation Guidelines
    • ⚓Local Deployment
      • Mock Identity System
      • Mock Relying Party
  • 🔌Interoperability
    • MOSIP
    • Inji
    • OpenCRVS
  • 🚀Roadmap and Releases
    • đŸ›Ŗī¸Roadmap
      • Roadmap 2025
      • Roadmap 2024
    • 📖Releases
      • v1.5.1
        • Test Report
      • v1.5.0
        • Test Report
      • v1.4.2
      • v1.4.1
        • Test Report
      • v1.4.0
        • Test Report
      • v1.3.0
        • Test Report
      • v1.2.0
        • Test Report
      • v1.1.0
        • Test Report
      • v1.0.0
        • Test Report
      • v0.9.0
        • Test Report
  • 🤝Community
    • Code Contribution
    • Code of Conduct
  • 📌General
    • 📚Resources
    • ❓FAQs
    • 💡Glossary
Powered by GitBook

Copyright Š 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.

On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Test
  2. Try It Out

Integrate with eSignet

Last updated 4 months ago

Was this helpful?

If you are a relying party looking to integrate with eSignet, you can connect with us by completing the here. This will assist us in facilitating a seamless integration on .

Here are some FAQs on the Google form.

What are redirect URIs?

The redirect URIs are the list of URIs the relying party provides where the authorization code needs to be sent after successful authentication by eSignet.

Why do you need a public key?

The public key shared by the relying party is used to verify the digital signature when there is an authorization request. It is also used to encrypt the user_info and send it to the relying party.

What is JWK format?

JWK (JSON Web Key) is a JSON data structure that represents a set of public keys utilizing either the Elliptic Curve or RSA families of algorithms (public key cryptography).

Learn more about JWK .

How can I convert a public key to JWK format?

Here is the easiest way to convert your public key (a .PEM file) to JWK format for testing.

  • Go to the link

  • Select Public Key Use as Signing

  • Select Algorithm as RS256

  • Select Key ID as alpha-numeric-random-string

  • Paste the public key PEM file content in PEM encoded key

  • Click on the convert button

Once you receive the eSignet credentials at the email address provided on the form, please go through our integration guide on to complete the integration.

🎮
đŸ•šī¸
form
collab
here
https://russelldavies.github.io/jwk-creator/
Relying Party Integration