[
https://issues.apache.org/jira/browse/TIKA-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526632#comment-17526632
]
Nicholas DiPiazza commented on TIKA-3725:
-----------------------------------------
[~tallison] in my case I have a bunch of other deployments and statefulsets
that are all using JWT to keep all inner-pod communication. so in my case
having the ability to be consistent with those would be nice.
> Add Authorization to Tika Server (Suggest Basic to start off with)
> ------------------------------------------------------------------
>
> Key: TIKA-3725
> URL: https://issues.apache.org/jira/browse/TIKA-3725
> Project: Tika
> Issue Type: New Feature
> Components: tika-server
> Affects Versions: 2.3.0
> Reporter: Dan Coldrick
> Priority: Minor
>
> I would be good to get some Authentication/Authorization added to TIKA server
> to be able to add another layer of security around the Tika Server Rest
> service.
> This could become a rabbit hole with the number of options available around
> Authentication/Authorization (Oauth, OpenId etc) so suggest as a starter
> basic Auth is added.
> How to store user(s)/password suggest looking at how other apache products do
> the same?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
