You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2020/05/23 15:11:15 UTC

[GitHub] [nifi] pvillard31 commented on pull request #4288: NIFI-7475 Initial commit for JWT bundle

pvillard31 commented on pull request #4288:
URL: https://github.com/apache/nifi/pull/4288#issuecomment-633073098


   Hey @dml872 - thanks a lot for this contribution. I was thinking about it (as I need something very similar at the moment) and I was wondering if it really makes sense to do that based on the flow file content.
   
   My thought process is the following: a user is making a request that is received through a ListenHttp or HandleHttpRequest processors. The HTTP request contains the `Authorization: Bearer <JWT>` header. I would then use the `UnsignJWT` processor to validate the JWT and retrieve the claims from the JWT payload. In my mind the `UnsignJWT` processor would have a property saying in which flow file attribute we have the `Bearer <JWT>` data, would unsign it, and would update the flow file by adding attributes to it with the claims contained in the JWT. If the JWT cannot be unsigned, the flow file would go to a failure relationship.
   
   Does it make sense? Do you have another use case in mind?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org