-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] Support for authorization via username/password #7
Comments
I believe this request will be addressed by the work done here: #8 |
As it turns out we are going to get support for client cert authentication but not for username/password authentication just yet. This needs to be added separately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Nifi has authentication enabled, using this plugin will be failed because access token is not passed when calling Nifi APIs. If config can be extended to include username and password, then call POST /access/token to get the access token, then pass the returned token as Authorization header when call Nifi APIs. The token lifetime lasts for 12 hours, token refresh handling may not be needed.
The text was updated successfully, but these errors were encountered: