We have a WebApi to approve requests (mostly in html/JavaScript/Appian) This page contains a table which has a link to download documents from filenet. It works fine for Application level roles but redirects to Appian sign in page for non-Application roles. We were told to fetch documents from Appian instead.
I created a post webapi(doc) which has start process(retrieve docs from filenet) and returns docId in json . This is working fine but when calling this webapi(doc) in Integration, it fails with 302. Provided basic auth, tried with serviceaccount as well.
Idea: create another get webapi to invoke this integration and call in approval page.
I'd appreciate if there are any other ways for non-Appian users to access documents can be given.
Any guidance will be appreciated. TIA.
Discussion posts and replies are publicly visible
Appian web APIs always require authentication by an Appian user or service account; there is no supported way to expose a web API endpoint with no authentication at all.
Not sure this is possible aside from having them access the filenet link directly (assuming they have FileNet access but no Appian access). If this is someone outside the org, you will have no choice but to build a custom API that calls Appian with a service account to stream the document back.