Hi Nifi Dev Team

 

I am new to the open source community and not really a developer, but have
developed 2 Nifi Customs processors to improve its support for APIs and API
Security.  Looking for some help from more experienced Nifi contributors to
review the code, and if appropriate contribute it to the base product. The
processors are.

 

1.      OAuth 2.0 JWT Token Validation Processor. Uses the RSA 256 Public
Key to validate the JWT signature then can optionally validate the Issuer
and Client ID, and if the Token is valid, extract claims into FlowFile
attributes based on a list provided to the processor. The full JWT decoded
claim (JSON) is also added as an attribute.  If the token has expired or is
invalid, details of the error are available in attributes for error
handling.
2.      OAS 3.0 API Validation Processor.  Accepts the Swagger API URL (OAS
JSON) to validate the HTTP Request against the API definition. If valid, it
will extract an URI Parms and URL Query Parms to FlowFile Attributes, as
well as the specific API interface operationId, which can then be use by the
RouteOnAttribute processor to pass each API interface to separate flow for
processing. If the request is invalid, details of the error are available in
attributes for error handling.

 

I am happy to provide the code and usage examples to anyone that would like
to validate the code and submit is for inclusion into the core Nifi product;
Thanks.

 

Kind Regards

 

Bryce Macdonald

 

 

Reply via email to