The Infinispan libraries included in AS7 are there because they form the foundation of the AS's clustering layer (web sessions, ejb stateful beans, etc) and JPA 2nd level caching. They are not exported by default to user deployments which should in fact package their own versions of the libraries. The REST war file provided in the distribution is only an example of how to use the infinispan-server-rest module to build an application which exposes caches via REST. For a proper implementation of REST within the scope of the AS (i.e. using the Infinispan subsystem, using the AS security layer, etc), look at our server project https://github.com/infinispan/jdg/

You should modify standalone.xml by replacing the following line

<rest-connector virtual-server="default-host" cache-container="local" security-domain="other" auth-method="BASIC" />

with

<rest-connector virtual-server="default-host" cache-container="local" />

or create the "other" security domain and add users there.

However my suggestion to look at JDG was not intended as "you should use this" , but rather as: JDG provides an implementation of an Infinispan REST endpoint in the context of an AS module.

But what I wanted to stress in particular was: cache containers and caches created by the AS Infinispan subsystem are not really meant to be used by user-deployments directly, but are only there to provide services to other AS subsystems. Although the AS documentation tells you how to access these caches from your apps (by tweaking the MANIFEST.MF file), the recommended way to use Infinispan in your applications is to include the JAR files in your WAR/EAR, so you can use whichever version you want, use all the features that are not distributed as AS modules and provide more detailed configuration.