Deeplink guests and Anonymous users

I have been searching for this answer for a while, but have not found a definitive answer: Is it a requirement that Anonymous users be enabled in my application in order to successfully use the 'Allow Guests' option in the Deeplink configuration? My application requires that users login to access everything, but there are a couple of pages that I would like to be publically available without the need to login through a deeplink. If I enable Anonymous users and 'Allow Guests', these deeplink will work, however, the login page is not always securing the rest of the application. With Anonymous users disabled (Allow Guests still enabled on the deeplink) I get a HTTP 500 error with the following stacktrace: java.lang.Exception: Guest login is not enabled     at deeplink.actions.StartDeeplinkJava$DeepLinkHandler.createGuestSession(     at deeplink.actions.StartDeeplinkJava$DeepLinkHandler.serveDeeplink(     at deeplink.actions.StartDeeplinkJava$DeepLinkHandler.processRequest(     at com.mendix.externalinterface.connector.MxRuntimeConnector$1.execute(     at com.mendix.externalinterface.connector.MxRuntimeConnector$1.execute(     at com.mendix.util.classloading.Runner.doRunUsingClassLoaderOf(     at com.mendix.externalinterface.connector.MxRuntimeConnector.processRequest(     at com.mendix.core.impl.MxRuntimeImpl.processRequest(     at com.mendix.m2ee.appcontainer.server.handler.RuntimeHandler.handle(     at org.eclipse.jetty.server.handler.HandlerList.handle(     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(     at org.eclipse.jetty.server.Server.handle(     at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(     at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(     at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(     at org.eclipse.jetty.http.HttpParser.parseNext(     at org.eclipse.jetty.http.HttpParser.parseAvailable(     at org.eclipse.jetty.server.AsyncHttpConnection.handle(     at     at$     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(     at org.eclipse.jetty.util.thread.QueuedThreadPool$     at   Deeplink version 5.1 is being used; same result using 4.5 previously. Looking for some guidance in troubleshooting this further. TIA
1 answers

My advise would be to look into Access Rights. Configure User Roles and Module Roles to specify the access to each part of the application. Furthermore you can restrict access through the Access Rules per entity. It can be a bit of a struggle, but it allows you to specify the exact access rules that you need.