[[_fuse_adapter_classic_war]] ==== Secure Classic WAR application The needed steps to secure your WAR are: * Declare needed security constraints in `/WEB-INF/web.xml` . You also need to declare login-config and all the roles inside security-role. The example configuration can look like this: [source,xml] ---- customer-portal index.html Customers /customers/* user BASIC does-not-matter admin user ---- * Add `jetty-web.xml` file with the authenticator to `/WEB-INF/jetty-web.xml` . Typically it will look like this: [source,xml] ---- ---- * Add `/WEB-INF/keycloak.json` with your {{book.project.name}} configuration. The format of this config file is described in the <> section. * Make sure your WAR imports `org.keycloak.adapters.jetty` and maybe some more packages in `META-INF/MANIFEST.MF` file in header `Import-Package`. It's recommended to use `maven-bundle-plugin` in your project to properly generate OSGI headers in manifest. Note that "*" resolution for package doesn't import `org.keycloak.adapters.jetty` package as it's not used by application or Blueprint or Spring descriptor, but it's used just in `jetty-web.xml` file. So list of the packages to import may look like this: [source, subs="attributes"] ---- org.keycloak.adapters.jetty;version="{{book.project.version}}", org.keycloak.adapters;version="{{book.project.version}}", org.keycloak.constants;version="{{book.project.version}}", org.keycloak.util;version="{{book.project.version}}", org.keycloak.*;version="{{book.project.version}}", *;resolution:=optional ----