I think you are looking for the SlingSettingService. See this thread: http://forums.adobe.com/thread/1020051

Hi,Please review the Oak documentation: http://jackrabbit.apache.org/oak/docs/security/authentication/externalloginmodule.html. You might also want to watch the recently held CQ Gems session on this topic: http://dev.day.com/content/ddc/en/gems/oak-s-external-login-module---authenticating-with-ldap-...

Hi,There's three separate elements here:Web server (where the actual clients get content)Dispatcher (the module in the web server which proxies requests to AEM)AEM's HTTP stack.#1 is available today using mod_h2: https://github.com/icing/mod_h2 and will be in the next release of Apache HTTPD. This i...

guruprasadg24550660 wrote... If we use external login module still we will have to create the users in AEM or can we do away with that?    In practice, yes. The External Login Module will basically handle this for you.

I agree with bsloki here that this shouldn't be an issue. You will, however, want to ensure you are using AEM 6.0 or higher and Oak. WIth Jackrabbit/CRX 2, such scale was possible, but you do need to do some extra configuration if you have groups with thousands of members. Your post didn't call this...

Keep in mind that the change Joerg is describing has absolutely nothing to do with ACLs. This is only for users and groups node names/path. The link between an ACL and a user/group was always done through the principal name.Any code which assumed that the path to a user or group was derivable from t...

Hi Mark,As I replied to you on Twitter, I'm not sure what you mean about "hashed paths" in the context of ACLs. If you are consistently losing ACLs on package installation, be sure you are specifying the right Access Control Handling. It should probably be Override. I think the default is Ingore. Yo...

No, this feature does not exist in Oak. See https://issues.apache.org/jira/browse/OAK-2544In general, you probably want to use node/resource iteration instead.

Ah shoot, I'm sorry. You are correct -- these are passed as headers, not request parameters. Should have spotted that originally.Incidentally, if you look at the replication log, you can see all the headers passed as part of the replication HTTP request.

Hi,Are you saying that for a POST request from the replication sender, you do not get any request parameters? Or that you do, but the values are all empty arrays?The code above looks like it should work to get the parameters, but it is a bit convoluted.I would just doString action = slingRequest.get...