Member since
04-05-2022
12
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3063 | 08-02-2022 07:03 AM |
10-16-2025
12:30 AM
Hi @vafs , > I think that version is not provided for Cloudera on the CFM right your right, but this platform was the best one so far for all NiFi questions 🤙 I will update this thread, if i got a solution, either if Cloudera or not
... View more
10-14-2025
11:41 PM
Hi guys, i've just started to work with parquet files, all is running with database own export logics, but they are not traceable - use NiFi was the Idea. Now im just annoyed how bad i am to handle this ... seems no default export available for this, install extensible-bundles ... NoClass here and there etc... Did anybody of you solved to add Parquet to NiFi 2.5.0? I've downloaded and provided nifi-parquet-nar-2.5.0.nar, nifi-hadoop-nar-2.5.0.nar and nifi-hadoop-libraries-nar-2.5.0.nar still NoClassDefFoundErrors in this order of log (single named) - org/apache/nifi/serialization/RecordSetWriterFactory - org/apache/nifi/processors/hadoop/AbstractFetchHDFSRecord - org/apache/nifi/processors/hadoop/AbstractPutHDFSRecord - org/apache/nifi/serialization/RecordReaderFactory - org/apache/nifi/serialization/RecordSetWriterFactory - org/apache/parquet/io/OutputFile - org/apache/parquet/io/InputFile Anybody who can helpt me?
... View more
Labels:
- Labels:
-
Apache NiFi
07-11-2023
02:07 AM
Hi guys, i've got time to check this behaviour! 🤗 Here my changes, which i only made and the AzureAD was requested. nifi@ad62a85cc576:/opt/nifi/nifi-current/conf$ diff nifi.properties nifi.properties.fresh
199c199
< nifi.security.user.oidc.discovery.url=https://login.microsoftonline.com/DirecotoryID/v2.0/.well-known/openid-configuration
---
> nifi.security.user.oidc.discovery.url=
202,203c202,203
< nifi.security.user.oidc.client.id=ApplicationID
< nifi.security.user.oidc.client.secret=ClientSecret
---
> nifi.security.user.oidc.client.id=
> nifi.security.user.oidc.client.secret=
205,207c205,207
< nifi.security.user.oidc.additional.scopes=profile
< nifi.security.user.oidc.claim.identifying.user=email
< nifi.security.user.oidc.fallback.claims.identifying.user=upn
---
> nifi.security.user.oidc.additional.scopes=offline_access
> nifi.security.user.oidc.claim.identifying.user=
> nifi.security.user.oidc.fallback.claims.identifying.user= That was only my first try. I will keep everyone up to date, if i got more infos
... View more
05-27-2023
02:49 AM
Hi, thx for your hints. AzureAD Login is already working, but I will check why after my vacations and keep this topic updated.
... View more
05-23-2023
11:08 PM
If nobody got a solution, that's okay, but does anybody got a hint for me to solve the authentication at the rest api of nifi regarding AzureAD OAuth2? *edited - fix typo*
... View more
05-19-2023
04:45 AM
Hi guys, i'm working on a NiFi 1.21.0 and the user login is connected to AzureAd. It's working a nice way for all humans, but we want to check the nifi with our monitoring solution. My login-identity-providers.xml contains <loginIdentityProviders>
<provider>
<identifier>single-user-provider</identifier>
<class>org.apache.nifi.authentication.single.user.SingleUserLoginIdentityProvider</class>
<property name="Username">known-user</property>
<property name="Password">hashed-known-password</property>
</provider>
</loginIdentityProviders> My authorizers.xml contains <authorizers>
<userGroupProvider>
<identifier>file-user-group-provider</identifier>
<class>org.apache.nifi.authorization.FileUserGroupProvider</class>
<property name="Users File">./conf/users.xml</property>
<property name="Legacy Authorized Users File"></property>
<property name="Initial User Identity 1"></property>
</userGroupProvider>
<userGroupProvider>
<identifier>aad-user-group-provider</identifier>
<class>org.apache.nifi.authorization.azure.AzureGraphUserGroupProvider</class>
<property name="Refresh Delay">5 mins</property>
<property name="Authority Endpoint">https://login.microsoftonline.com</property>
<property name="Directory ID">DirectoryID</property>
<property name="Application ID">ApplicationID</property>
<property name="Client Secret">ClientSecret</property>
<property name="Group Filter Prefix">Nifi-AAD</property>
<property name="Page Size">100</property>
</userGroupProvider>
<userGroupProvider>
<identifier>composite-configurable-user-group-provider</identifier>
<class>org.apache.nifi.authorization.CompositeConfigurableUserGroupProvider</class>
<property name="Configurable User Group Provider">file-user-group-provider</property>
<property name="User Group Provider 1">aad-user-group-provider</property>
</userGroupProvider>
<accessPolicyProvider>
<identifier>file-access-policy-provider</identifier>
<class>org.apache.nifi.authorization.FileAccessPolicyProvider</class>
<property name="User Group Provider">composite-configurable-user-group-provider</property>
<property name="Authorizations File">./conf/authorizations.xml</property>
<property name="Initial Admin Identity">admin@login-domain.com</property>
<property name="Legacy Authorized Users File"></property>
<property name="Node Identity 1"></property>
</accessPolicyProvider>
<authorizer>
<identifier>managed-authorizer</identifier>
<class>org.apache.nifi.authorization.StandardManagedAuthorizer</class>
<property name="Access Policy Provider">file-access-policy-provider</property>
</authorizer>
<authorizer>
<identifier>single-user-authorizer</identifier>
<class>org.apache.nifi.authorization.single.user.SingleUserAuthorizer</class>
</authorizer>
</authorizers> The nifi.properties contains nifi.authorizer.configuration.file=./conf/authorizers.xml
nifi.security.user.authorizer=single-user-authorizer
nifi.security.allow.anonymous.authentication=false
nifi.security.user.saml.authentication.expiration=12 hours
nifi.security.user.authorizer=single-user-authorizer
nifi.security.user.login.identity.provider=single-user-provider
nifi.security.user.jws.key.rotation.period=PT1H
nifi.security.user.oidc.discovery.url=https://login.microsoftonline.com/DirecotoryID/v2.0/.well-known/openid-configuration
nifi.security.user.oidc.connect.timeout=5 secs
nifi.security.user.oidc.read.timeout=5 secs
nifi.security.user.oidc.client.id=ApplicationID
nifi.security.user.oidc.client.secret=ClientSecret
nifi.security.user.oidc.preferred.jwsalgorithm=
nifi.security.user.oidc.additional.scopes=profile
nifi.security.user.oidc.claim.identifying.user=email
nifi.security.user.oidc.fallback.claims.identifying.user=upn My Questions: 1) Is it possible to login with the "known user" of login-identity-providers.xml? 2) How can I access the api? Thank you for your time!
... View more
Labels:
- Labels:
-
Apache NiFi
-
Security
08-02-2022
07:03 AM
1 Kudo
I've created a simple processor on my own => https://github.com/mbraunerDE/nifi-plugins/blob/4cd76e047af88e2ec84f51c883b40f74d1bb9ef0/nifi-mbrauner-plugins-processors/src/main/java/de/mbrauner/nifiplugins/processors/ListSFTPWithInput.java
... View more
07-10-2022
11:55 PM
Hi @SAMSAL , thank you for your help, but you're absoluty right in your second post - the first one seems very "uncomfortable". @MattWho: I really don't care about the content, i've created backup-files in the stages before mailing and only the consumed filenames are relevant for mail. Last time there was 350 files and 35MB for backup 😉
... View more
07-08-2022
06:19 AM
Hi guys, i've got a queue containing ~1000 files and i want to receive a mail with all ~1000 filenames. I don't care about the content of all files, only the ${filename} should be put on a list and send as content. Example: - Queue Position 1 - filename: first.xml - Queue Position 2 - filename: second.xml - Queue Position 3 - filename: third.xml Resulting mail content (possibility 1): - first.xml - second.xml - third.xml Resulting mail content (possibility 2): first.xml, second.xml, third.xml Something just like a list of filenames in queue. Dies anybody got an idea how to solve without many api-magic? Greetings and best regards - Max
... View more
Labels:
- Labels:
-
Apache NiFi
04-06-2022
06:14 AM
Hey steven-matison, Thank you for the reply, but I think that way is more complicated to get it supported over multiple versions and easy to understand for my next-year-me.
... View more