Enable anonymous access for testing Mobile Forms

IconSometimes it’s easier to enable anonymous unsecured access to pages, assets, etc for testing and quick demos so you don’t have to keep logging in via the SSO screen. After playing with the user security in CQ/CRX in Livecycle ES4, you soon discover that just giving the anonymous user access to your pages or assets isn’t enough to make this happen.  You have to explicitly allow access to these resources from within the OSGi configuration in the Adobe CQ Web Console.

If you want to allow anonymous access to your resources then do the following:

  1. Open OSGi console:  http://[server]:[port]/lc/system/console/configMgr
  2. Search for Apache Sling Authentication Service Bundle
  3. Click the bundle to open it
  4. Ensure Allow Anonymous Access is checked
  5. Under Authentication Requirements section, you need to add an entry that starts
    -/content/node/you/want/to/allow/anonymous/access/to” (without quotes)
  6. Click Save

    Apache Sling Authentication Service

    Apache Sling Authentication Service

  7. Open CQ5 Security:  http://[server]:[port]/lc/useradmin
  8. Double click the everyone group
  9. On the right, click the Permissions tab
  10. Browse to the content node you allowed above
  11. Add the rights you require for the anonymous user (usually its just Read)
  12. Click Save
    CQ5 Security

    CQ5 Security


About Darren
I am a Senior Consultant and for BizTECH Enterprise Services (Australia) specialising in AEM Forms and Adobe LiveCycle, Document Services and Adobe Experience Manager.

4 Responses to Enable anonymous access for testing Mobile Forms

  1. Thank you so much. Everyone has told about sling authentication but no one has put the point to add read to everyone group. It worked for me.

    • Darren says:

      Thanks for the feedback Deeptesh. Note that if you are publishing your forms to a normal Publish/Dispatcher combo, you will find that they are all anonymous access by default in /content. So you only ever really need to do this if you are providing sample access via Author or Workflows server or if you have secured access to your content on your Publish instance using LDAP, SAML or similar.

  2. Hello Darren! I’ve got a question on setting up an Adobe XFA mobile app to run on SSL (Adobe LiveCycle ES4). We have valid SSL certificates loaded into the CACERTS, truststore.jks, and local server.jks; we’ve configured the JBOSS server.xml with the right store path and passwords; and everything seems to be set up in the admin UI. We are also running on a Windows 2008R2 server with IIS 7.0. When we launch the application it opens up with https. However, when the application makes a callback to the server, the application only renders on port 8080. When I launch the aggregated link that combines the html to the XML data, then we receive a JAVA exception error that says that it cannot server a request to the profiles/default.html in /render/get.jsp. In bold at the top, it says error while executing script formBody.jsp.

    Does this look more like a permissions issue, a sling configuration issue, or something with Rights Management perhaps. I was hoping to get a fresh perspective. Any insight would be greatly appreciated.


    – Mike Archer

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


Everything AEM aka CQ5 based on my experience listed here.

Adobe AEM The Right Way

Best practices, tips, and tricks for your Adobe AEM project


A WCM journey with Day/Adobe CQ

Technoracle (a.k.a. "Duane's World")

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

Adobe LiveCycle Blog

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.


A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

Code Monkey

Ramblings of a Developer

%d bloggers like this: