Member since
09-03-2020
126
Posts
7
Kudos Received
0
Solutions
02-09-2024
08:14 AM
1 Kudo
@bhara Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
01-15-2024
07:44 AM
Could you please get the full processor error in the nifi-app.log, that will provide more details to understand the exception?
... View more
12-05-2023
04:26 AM
The message means that the authentication is valid, but the user is not authorized to use the topic. Can you confirm what authorizer are you using and the current oauth configuration?
... View more
09-14-2023
07:25 PM
Its ListFile.
... View more
09-14-2023
11:10 AM
1 Kudo
@LKB You would get better traction/feedback if you start your own community question. Your query is not very related to issue in this post. As far as the one question related to this post about encrypted manager password, @mks27 simply masked it by using "***" in his post. NiFi does not replace actual password with * when encrypting sensitive passwords. The NiFi Encrypt-Config Toolkit can be used to encrypt passwords used in various NiFi configuration files: https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#encrypt_config_tool Thank you, Matt
... View more
07-14-2023
02:27 PM
@shamika NiFi based authorization is case sensitive. 2023-07-12 10:46:40,800 INFO [NiFi Web Server-19] o.a.n.w.a.c.AccessDeniedExceptionMapper identity[myuser], groups[bigG, bigdGer] does not have permission to access the requested resource. No applicable policies could be found. Returning Forbidden response the nifi-user.log is telling you that your successfully authenticated user "myuser" is known by NiFi to belong to groups "bigG" and "bigdGer". In Ranger you'll need to make sure that yoru user "myuser" or one of these groups "bigG" and/or "bigdGer" has been authorized for "READ" on the "/flow" NiFi resource Identifier. If Ranger has the group as "bigg" or "BIGG", "bigDGER", etc it will not work because NiFi is case sensitive. You could also share your authorizers.xml if you'd like use to verify your configuration there. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
10-23-2022
03:55 AM
How did anyone solve this issue? I was currently trying to solve similar issue via nifi api (Postman)
... View more
09-01-2022
03:22 AM
Thank you Matt sorry for the super delay response but it's very helpful
... View more
07-13-2022
05:16 AM
Hello Matt, Thank you ! this solved the error (now I'm facing another one, but will figure it out 🙂 ). For further reference I had to configure those 3 lines in nifi.properties : nifi.security.identity.mapping.pattern.dn=^CN=(.*?), OU=(.*?) nifi.security.identity.mapping.transform.dn=NONE nifi.security.identity.mapping.value.dn=$1@$2 Thanks. Vince.
... View more
06-09-2022
06:21 AM
The error says the Connection pool is not able to find configured driver classpath name into provided database client-jar driver. Please check and make sure configured driver classpath name is present on the provided jar file.
... View more