Hi guys Based on your request it’s not clear for me whether your REST API use Client Certificates to authenticate/authorizer or not. I assume not, typically you’’ must import the CA Public Key (where the REST API has been signed with) into a java truststore (JKS) which you assign to the InvokeHTTP “SSL Context Service”. That truststore is only to get a trusted/secured SSL connection, nothing else. Next step is to authorize, in a lot of cases you insert username/password to get a token, or as you call it “API key password”. This token is typically valid for a short period of time. So to sum it up, it isn’t clear what exactly you are looking for, your information isn’t clear enough, at least for me. Where and how did you get this “API key password”
Cheers Josef From: Luca Giovannini via users <users@nifi.apache.org> Date: Monday, 23 September 2024 at 15:31 To: users@nifi.apache.org <users@nifi.apache.org> Subject: R: API key NiFi Be aware: This is an external email. Hi All, any insights/help on this? Anything would help us a lot! Thank you, Luca Luca Giovannini Information Systems Analyst Deda Next www.linkedin.com/in/lucagio/<http://www.linkedin.com/in/lucagio/> Mobile +39.347.7993183 Via Marco Emilio Lepido 178, 40132 Bologna, Italy https://www.dedanext.it/ [Deda Next] Da: Simone Sablone via users <users@nifi.apache.org> Inviato: lunedì 9 settembre 2024 13:07 A: users@nifi.apache.org Oggetto: API key NiFi Hi All, I need to access to an HTTP API endpoint protected with an "API Key" authorization protocol and I am rather new to all of this. I have a .CRT certificate, a .CER certificate, a .PFX file and corresponding password, and API Key password (key and value pair). I am able to make it work with Postman, but I can't figure out how to do it with NiFi. I know I have to use an "Invoke HTTP" processor, probably with an SSL Context Service, but I can't fugure out how to configure them. Can you help me? Thank you very much for your support. Simone Sablone – Data Scientist - Dedagroup M 339 6812735 | https://www.linkedin.com/in/simone-sablone-b5a7a1130 Dedagroup Spa – Sede di Roma, Via Paolo di Dono 73 www.deda.group<http://www.deda.group/> [cid:image002.png@01DB0DCD.7DBAEA20]<https://www.deda.group/home> Le informazioni contenute in questo messaggio di posta elettronica sono riservate e confidenziali e ne e' vietata la diffusione in qualsiasi modo o forma. Qualora Lei non fosse la persona destinataria del presente messaggio, La invitiamo a non diffonderlo e ad eliminarlo, dandone gentilmente comunicazione al mittente. The information included in this e-mail and any attachments are confidential and may also be privileged. If you are not the correct recipient, you are kindly requested to notify the sender immediately, to cancel it and not to disclose the contents to any other person.
smime.p7s
Description: S/MIME Cryptographic Signature
