Hello list,
I have resolved first problem about cache_peer using Kerberos
authentication. Now I want to make that setup transparent/intercepting.
Keep in mind that my situation does NOT involve browsers or port 80 at any
point, it's a pure machine-to-machine API communication.
I have added the "i
in a continuous "401 Unauthorized" loop.
I have more problems but will start a separate question for that.
On Thu, Mar 15, 2018 at 12:53 PM, Amos Jeffries
wrote:
> On 15/03/18 23:52, Patrick Nick wrote:
> > Thanks Amos, this sounded promising. Unfortunately the behavior I
> >
ed to happen?
Or am I not configuring it right? (The keytab is readable by the squid user)
On Thu, Mar 15, 2018 at 9:44 AM, Amos Jeffries wrote:
> On 15/03/18 11:01, Patrick Nick wrote:
> > It consumes the data for its graphs from a REST API via HTTP, on ports
> > in the 8000-9000 ra
ation?
>
> Am 14. März 2018 19:27:48 MEZ schrieb Patrick Nick >:
>>
>> Hi Enrico,
>>
>> You write
>>
>>> But squid cannot authenticate those requests on the destination server
>>> if it needs authentication as well.
>>
>>
>&g
trict it to both, src and destination and additionaly specific
> ports. But squid cannot authenticate those requests on the destination
> server if it needs authentication as well.
>
> Best regards,
> Enrico
>
>
> Am 14. März 2018 18:58:54 MEZ schrieb Patrick Nick >:
Hello list,
We are in the process of Kerberizing our Big Data operation, but we have a
GUI tool in use that is not capable of Kerberos authentication. I'm looking
for a way to keep using it, which means that it needs to read data from a
Kerberos-protected service.
To be clear, I'm looking for a p
