rabbit-dev as this doesn't really belong to
>> the sling list)
>>
>>>>> I just try to connect with the standard command line utility via davex
>>>>> to the repository.
>>>>>
>>>>> java -jar jackrabbit-standalone-2.3.1-SNAPSH
y belong to
> the sling list)
>
>>>> I just try to connect with the standard command line utility via davex
>>>> to the repository.
>>>>
>>>> java -jar jackrabbit-standalone-2.3.1-SNAPSHOT.jar --cli
>>>> http://localhost:8080/ser
ymous user everything is fine and I can
logout/login with admin.
With the anonymous user disabled I still can login but I can not do
any writes as the davex layer couldn't properly detect the
capabilities of the repository.
IIUC this is because although there was a change in Jackrab
hanges required in Sling Authentication to
>> support the DavEx servlet will benefit other use cases.
>
> Well, there is a unique "feature" which is called "missing-auth-mapping". I
> am not entirely sure, that I want to add support for such functionality.
> Because
ue
>>>> and that *if* there are changes required in Sling Authentication to
>>>> support the DavEx servlet will benefit other use cases.
>>>
>>> Well, there is a unique "feature" which is called "missing-auth-mapping". I
>>> am n
; servlet with respect to Sling Authentication are not entirely unique
>>> and that *if* there are changes required in Sling Authentication to
>>> support the DavEx servlet will benefit other use cases.
>>
>> Well, there is a unique "feature" which is calle
vlet will benefit other use cases.
>
> Well, there is a unique "feature" which is called "missing-auth-mapping". I
> am not entirely sure, that I want to add support for such functionality.
> Because in essence, this would just replace one "anonymous" user wit
y sure, that I want to add support for such functionality. Because
in essence, this would just replace one "anonymous" user with another one (with
maybe the added functionality of being able to disable that user...).
>
> I'm convinced the problems are entirely solvable a
t;>> On Wed, Nov 9, 2011 at 3:11 PM, Felix Meschberger
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> Am 09.11.2011 um 12:56 schrieb Markus Joschko:
>>>>>
>>>>>> With the most recent changes (SLING-2274) I can ag
>>> Hi,
>>>>
>>>> Am 09.11.2011 um 12:56 schrieb Markus Joschko:
>>>>
>>>>> With the most recent changes (SLING-2274) I can again use the CLI
>>>>> client over davex,
>>>>> but only when the anonymous user is enabl
;
>>>> With the most recent changes (SLING-2274) I can again use the CLI
>>>> client over davex,
>>>> but only when the anonymous user is enabled. As soon as I disable it,
>>>> I again have the problem with the repository descriptor retrieval.
&g
;
>>>> With the most recent changes (SLING-2274) I can again use the CLI
>>>> client over davex,
>>>> but only when the anonymous user is enabled. As soon as I disable it,
>>>> I again have the problem with the repository descriptor retrieval.
&g
>>> With the most recent changes (SLING-2274) I can again use the CLI
>>>> client over davex,
>>>> but only when the anonymous user is enabled. As soon as I disable it,
>>>> I again have the problem with the repository descriptor retrieval.
>>
> client over davex,
>>> but only when the anonymous user is enabled. As soon as I disable it,
>>> I again have the problem with the repository descriptor retrieval.
>>
>> Hmm, this is not how it is intended to be. The davex bundle registers a
>> dummy service whic
> client over davex,
>>> but only when the anonymous user is enabled. As soon as I disable it,
>>> I again have the problem with the repository descriptor retrieval.
>>
>> Hmm, this is not how it is intended to be. The davex bundle registers a
>> dummy service whic
On Wed, Nov 9, 2011 at 3:11 PM, Felix Meschberger wrote:
> Hi,
>
> Am 09.11.2011 um 12:56 schrieb Markus Joschko:
>
>> With the most recent changes (SLING-2274) I can again use the CLI
>> client over davex,
>> but only when the anonymous user is enabled. As soon as
Hi,
Am 09.11.2011 um 12:56 schrieb Markus Joschko:
> With the most recent changes (SLING-2274) I can again use the CLI
> client over davex,
> but only when the anonymous user is enabled. As soon as I disable it,
> I again have the problem with the repository descriptor retrieval.
With the most recent changes (SLING-2274) I can again use the CLI
client over davex,
but only when the anonymous user is enabled. As soon as I disable it,
I again have the problem with the repository descriptor retrieval.
However I have a customer requirement that is: Nobody should be able
to
OK, forget about it. The fix
https://issues.apache.org/jira/browse/JCR-3076 on trunk also works for
this problem.
On Fri, Oct 7, 2011 at 2:25 PM, Markus Joschko wrote:
> I just stumbled upon the anonymous user and that is virtually
> impossible to delete it, as it is recreated on
I just stumbled upon the anonymous user and that is virtually
impossible to delete it, as it is recreated on every repository start.
It is also not possible to change the password for the anonymous user.
So the only chance to get the site secured is to disable the anonymous
user, so nobody can
On Mon, Jun 28, 2010 at 10:57 AM, Marco Filosi
wrote:
> Hi,
>
> I removed the anonymous user but when I restart the servlet container (e.g.
> tomcat) the anonymous user is recreated. I need to know how I can remove
> anonymous user permanently if it is possible.
>
> Here belo
Hi,
I removed the anonymous user but when I restart the servlet container (e.g.
tomcat) the anonymous user is recreated. I need to know how I can remove
anonymous user permanently if it is possible.
Here below I explain the steps followed:
1. Get a list of users by calling curl -X GET
22 matches
Mail list logo
