Hi Rory,

I am facing the same problem. Any sample code reference to set the node ACL
for "anonymous" user with the writing permission would be really helpful.

Regards,
Sujoy Bhattacharjee

-----Original Message-----
From: Rory Douglas [mailto:[email protected]] 
Sent: Friday, February 06, 2009 8:11 PM
To: [email protected]
Subject: Re: How to disable login Pop-Up

Hello Nitesh

If you enter the credentials one time, they should be perisisted by your 
browser for the whole session across all paths.  If that's not 
happening, something strange is happening.  Note that the credentials 
you enter for the Felix console (/system/console) are not for the same 
realm, so you need to separately authenticate to the repository for 
other paths.

I think you'd usually want people to authenticate to a blogging app, so 
I assume this is for development purposes.  There are a few things you 
can do:

1) a) Enable anonymous access in the Request Authenticator AND
    b) Set the node ACLs appropriately so "anonymous" is allowed to 
write to them.  (You should be able to use the AccessControlUtil 
getUserManager(Session) and and getAccessControlManager(Session) methods 
to create/get the anonymous user & setup the ACLs.)

2)  If you really just want to write everything as one configured user & 
never have people login, you could implement a dummy 
AuthenticationHandler that just returns those default credentials for 
every request.  Register that handler for the "/" path and uninstall the 
HTTP Auth bundle.

Regards,
Rory

Nitesh Ambuj wrote:
> Hi All,
>
> I have created a Blog application on Sling Framework but it keeps on
popping
> the window for login credentials. 
>
> Could you please let me know how to disable the popup asking for sling
> credentials  (admin/admin)? 
>
> I guess this can be done by the allowing the anonymous user at the Felix
> configuration console.  
>
> But when I trying to write something it's throwing me error because
> anonymous don't have the write permission on the repository. 
>
> Thanks & Regards,
> Nitesh Ambuj 
>
>   

Reply via email to