# idp-to-abesid
Add ABES ID based on IDP.
# Enriched fields
Name | Type | Description |
---|---|---|
abes-id | String | ABES ID. |
# Prerequisites
# Prerequisites
idp-to-abesid enrichment middleware needs idp in ec.
You must use idp-to-abesid after filter, parser, deduplicator middleware.
# Headers
- idp-to-abesid-source-field : Fields in the ec for enrichment. "login" by default.
- idp-to-abesid-enriched-field : Enriched fields in the CE. "abes-id" by default
# Example
# How to use
# ezPAARSE admin interface
You can add idp-to-abesid by default to all your enrichments, To do this, go to the middleware section of administration.
# ezPAARSE process interface
You can use idp-to-abesid for an enrichment process. You just add the middleware.
# ezp
You can use idp-to-abesid for an enrichment process with ezp (opens new window) like this:
# enrich with one file
ezp process <path of your file> \
--host <host of your ezPAARSE instance> \
--settings <settings-id> \
--header "ezPAARSE-Middlewares: idp-to-abesid" \
--out ./result.csv
# enrich with multiples files
ezp bulk <path of your directory> \
--host <host of your ezPAARSE instance> \
--settings <settings-id> \
--header "ezPAARSE-Middlewares: idp-to-abesid"
# curl
You can use idp-to-abesid for an enrichment process with curl like this:
curl -X POST -v http://localhost:59599 \
-H "ezPAARSE-Middlewares: idp-to-abesid" \
-H "Log-Format-Ezproxy: <line format>" \
-F "file=@<log file path>"