Skip to content

Releases: GLEIF-IT/vlei-verifier-router

0.1.1 - Added Signed header verification and Presentations history endpoint

06 Apr 10:03
@aydarng aydarng
0.1.1
7086987
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
0.1.1 - Added Signed header verification and Presentations history endpoint Latest
Latest

Release Notes: vlei-verifier-router 0.1.1

We are pleased to release v0.1.1 of the vlei-verifier-router, introducing enhanced security and improved visibility into verification activity.

What’s New

🔐 Signed Headers Verification for /authorizations

  • Implemented verification of signed HTTP headers for /authorizations requests.

  • Strengthens security by ensuring that only authorized and authenticated clients can submit authorization requests.

📜 New /presentations_history Endpoint

  • Added the /presentations_history endpoint.

  • Allows clients to retrieve the history of credential presentations.

Assets 2
Loading

v0.1.0 - Vlei Verifier Router

05 Mar 13:58
@aydarng aydarng
0.1.0
dca6d44
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v0.1.0 - Vlei Verifier Router

Release Notes: vlei-verifier-router 0.1.0

We are excited to announce the first release (v0.1.0) of the vlei-verifier-router! This release marks a significant milestone in enabling scalable and fault-tolerant credential verification by acting as a load balancer and orchestrator for multiple vlei-verifier instances.

Key Features

1. Load Balancing

  • Distributes incoming verification requests across multiple vlei-verifier instances.

  • Ensures even traffic distribution, preventing any single instance from being overwhelmed.

2. Health Checks

  • Monitors the health of vlei-verifier instances.

  • Automatically routes traffic only to healthy instances, improving fault tolerance.

3. Dynamic Instance Management

  • Supports dynamic addition and removal of vlei-verifier instances.

  • Easily scale up or down based on demand.

4. Redis Support

  • Stores all AID-to-verifier mappings in Redis for persistence and scalability.

  • Enables efficient management of mappings and ensures data consistency across instances.

5. Compatibility with vlei-verifier-client

  • Exposes the same set of endpoints as the vlei-verifier, ensuring seamless integration with existing clients.

  • No changes are required to the vlei-verifier-client to switch to the router.

6. High Availability

  • Enables high availability by deploying multiple vlei-verifier instances behind the router.

  • Provides redundancy and failover capabilities.

Prerequisites

  • Docker installed on your system.

  • One or more vlei-verifier instances running.

  • A Redis server for storing mappings.

Loading