Red Hat Integration - Service Registry
  • Preface
  • Installation
    • Setting Up Project
    • PostgreSQL Database Deployment
      • Install Crunchy Postgres for Kubernetes Operator
      • Deploy PostgreSQL Database
    • Service Registry Deployment
      • Install Service Registry Operator
      • Configuring Service Registry
  • Testing
    • Testing Service Registry
    • REST API Testing Using Postman
    • Performance Testing Using hey
  • Security
    • Securing Service Registry
    • Red Hat Single Sign-On Deployment
      • Installing Red Hat Single Sign-On Operator
      • Deploy Red Hat Single Sign-On
      • Create Keycloak Realm For Service Registry
    • Configuring Service Registry
      • Service Registry with HTTPS
      • Service Registry without HTTPS (less secure)
      • Configuring Service Registry
      • Enable HTTP Basic Authentication
      • Enable Annonymous Read Access
      • Enable Role-Based Authorization
    • Testing Secure Service Registry API
  • Client Application
    • Create SSO Client for Application
    • Kafka Client Application
  • Appendix
    • CRD References
    • Installation Helper Script
    • Service Registry & SSO Integration with Self-Signed Certificate
Powered by GitBook
On this page
  1. Testing

REST API Testing Using Postman

PreviousTesting Service RegistryNextPerformance Testing Using hey

Last updated 2 years ago

This guide has provided a Postman collection with some example of requests to interact with the Service Registry via REST API calls. You can import the Postman collection and Postman environment files to Postman application as explained in the Postman official guide here.

Postman collection uses environment to store some variables i.e. hostname, API, group etc. which are used by each request in the collection. So, once you've imported the collection and environment files, you need to update the SERVICE_REGISTRY_HOST and GROUP variables in the Postman environment as a screenshot below before testing the Service Registry.

Postman
Postman