TRUE Connector
CtrlK
  • TRUE Connector
    • Prerequisite
    • Introduction
    • System requirements
    • Volumes
    • Default configuration
    • Starting and stopping containers
    • Component overview
  • REST API
  • Connector reachability
    • Connector ID
  • How to Exchange Data
  • Modifying configuration
    • Hostname validation
    • SSL/HTTPS
    • Change message format - Multipart/Mixed, Multipart/Form, Http-headers
    • WebSocket configuration (WSS)
    • IDSCPv2 configuration
    • Self Description validation
  • Advanced configuration
    • Supported Identity Providers
    • Extended jwt validation
    • Convert keystorage files
    • Validate protocol
    • Clearing House
    • Broker
    • Usage Control
    • MyData Usage Control
    • Audit logs
    • Firewall
    • NTP Server setup
    • Manage OS users
  • Contract Negotiation - simple flow
    • Get offered resource
    • Description Request Message
    • Contract Request Message
    • Contract Agreement request
    • Get offered resource after access is granted
  • Self Description API
    • Changing API password
    • Postman collection
  • License
  • Advanced doc
    • MYDATA_USAGE_CONTROL
    • PostgreSQL Configuration
    • Test cases
    • REST API
    • Testbed
    • Step to replicate True Connector installation in minikube.
    • Docker image signing and verification
  • Life cycle
  • Security
  • Roadmap
  • Traceability matrix
  • License
  • Contributing TRUE Connector
Powered by GitBook
On this page
  1. Modifying configuration

IDSCPv2 configuration

TRUE Connector can exchange data using IDSCPv2 protocol, currently only between ECC's, not between DataApp and ECC. To do this, modify following properties:

# Enable WSS between ECC
WS_ECC=false

# Enable IDSCPv2 between ECC - set WS_ECC=false
IDSCP2=true

Last updated 2 years ago