Hello Primiano, Joel, Lonnie and Aite,
We don't currently officially support this feature. However, we are developing support for it and there's a way to try it out on an experimental basis. As an experimental feature, it's not documented in the official SDC docs. We plan on adding this feature in the future, but as it is experimental, we can't guarantee that it will be added, or that it will retain the present form.
Before trying it out there are a few important security notes:
- You are enabling access to your resource with no authentication. This means that incoming requests will not be checked to verify that they come from an authenticated user. You must take precautions to ensure that no unexpected access is enabled by turning on this feature.
- Carefully look at the entire rule definition to make sure that the level of unauthenticated access is appropriate for the resource. You can restrict access to only a specific set of AppEngine IDs, for example, or only applications within your domain (<allowOutsideDomainAccess>false</allowOutsideDomainAccess>).
- Do NOT combine this feature with <allowAnyAppId>true</allowAnyAppId> unless you want ALL App Engine Apps written by any author to have unrestricted access to your resource.
Here's how to use it. In your resourceRules.xml file, add this to the rule definition:
<allowAnonymousAccess>true</allowAnonymousAccess>
A fuller example:
<resourceRules>
<rule repeatable="true">
<ruleNum>1</ruleNum>
<agentId>agentId1</agentId>
<allowDomainViewers>true</allowDomainViewers>
<allowOutsideDomainAccess>false</allowOutsideDomainAccess>
<allowAnonymousAccess>true</allowAnonymousAccess>
<apps repeatable="true">
<container>AppEngine</container>
<appId>REPLACE-WITH-APPID</appId>
</apps>
<url>REPLACE-WITH-URL</url>
<urlMatch>HOSTPORT</urlMatch>
</rule>
Please let us know if this works for you or not, we'd love to get feedback on it!
Thank you,
-Eric Pollmann