Jakob,
Thank you for your answer. So the patch I did was to allow one Marmotta module
that I am developping to call another existing marmotta module, which seems a
common use case for me when developping new modules in this SOA architecture.
Thank you for your proposal that I will try: "decrypt
Hi Fabian,
sorry, I mixed up the two. ClientConfiguration is the right one.
So you want to forward the auth-token you receive on your side to marmotta?
This usecase is currently not covered, the patch you did looks like a
possible solution.
A different approach would be to "decrypt" the auth tok
Jakob,
Do we talk here about ClientConfiguration or ConfigurationClient ?
In my understanding ConfigurationClient is a client to access the configuration
of Marmotta whereas I was talking about ClientConfiguration here.
In my code, to call the ImportClient, I am doing:
ClientConfiguration co
It is - setting the username/passwd in the ConfigurationClient should
do the trick.
I had a look into
org.apache.marmotta.client.clients.ConfigurationClient and
org.apache.marmotta.client.util.HTTPUtil, this is where I found the
warnings.
We updated HttpClient to 4.3 some time ago which changed t
Do you mean that passing the user/pwd to the ClientConfiguration should be the
correct way to do it ?
And, more precisely, where is the use of a deprecated API of HttpClient ?
thanks
Fabian
>>> Jakob Frank 27.10.2014 09:38 >>>
Hi Fabian,
while looking into the code for the data-import issue
Hi Fabian,
while looking into the code for the data-import issue, I saw that we
are using a deprecated API of HttpClient - maybe the authentication
issue is related to that.
Would be great if you could have a look into that and maybe provide a patch!
Best,
Jakob
On 24 October 2014 13:56, Fabia
