Skip to content
master
midpoint-connectors/connector-amqp-import/
midpoint-connectors/connector-amqp-import/

README

# AMQP Import Connector for midPoint

This is a proof of concept for integrating AMQP messages
into midPoint as a source for registry entries. Currently
it implements a very minimal sample of the TIER minimal
registry schema published in:

https://github.internet2.edu/TIER/schema/blob/master/schema/core-person.json

{
  "name": {
    "familyName": "Jansen",
    "givenName": "Jo",
    "middleName": "ethan",
    "nameType": "Legal"
  },
  "birthDate": "1955-12-10",
  "logon-id": "jjansen",
  "subject-id": "34-546877",
  "priorSubject-id": [
    {
      "id": "34-546876"
    }
  ],
  "sourceId": [
    {
      "id": "357A225",
      "source": "SIS"
    },
    {
      "id": "jansen121",
      "source": "HR"
    }
  ],
  "email": [
    {
      "emailAddress": "jjansen@goo.edu",
      "emailType": "primary"
    }
  ],
  "phone": [
    {
      "phoneNumber": "9194450056",
      "phoneType": "Work"
    },
    {
      "phoneNumber": "9194481296",
      "phoneType": "Mobile"
    }
  ],
  "personalPronoun": "Mr"
}

The connector currently supports DeleteOp, SearchOp<String>, SchemaOp, TestOp
with DeleteOp not having any actions, import operations are supported
by the SearchOp.

__NAME__ currently set to required email attribute.
__UID__ set to sourceId attribute, a concatenation of source + '-' + id.

The configuration class supports items that are described in

* src/main/resources/edu/unc/polygon/connector/amqp/Messages.properties

A sample configuration XML is in the samples directory.
You can’t perform that action at this time.