Merge pull request #22 from aasingh/master

added master-docinfo.xml and metadata.ini

master-docinfo.xml

@@ -0,0 +1,12 @@
+<productname>Red Hat Single Sign-On</productname>
+<productnumber>7.0.0</productnumber>
+<subtitle>Securing Applications and Services Guide</subtitle>
+<title>Securing Applications and Services Guide</title>
+<release>7.0.0</release>
+<abstract>
+	    <para>This guide consist of information for securing applications and services using Red Hat Single Sign-On 7.0.0</para>
+    </abstract>
+<authorgroup>
+    <orgname>Red Hat Customer Content Services</orgname>
+</authorgroup>
+<xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

metadata.ini

@@ -0,0 +1,20 @@
+[source]
+language = en-US
+type = book
+markup = asciidoc
+
+[metadata]
+title = Securing Applications and Services Guide
+product = Red Hat Single Sign-On
+version = 7.0.0
+edition = 
+subtitle = 
+keywords = 
+abstract = 
+
+[bugs]
+reporting_url = 
+type = 
+product = 
+component = Documentation
+

topics/oidc/java/jboss-adapter.adoc

@@ -174,6 +174,7 @@ public class CustomerService {
 This section describes how to secure a WAR directly by adding config and editing files within your WAR package. 
 
 The first thing you must do is create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
+
 The format of this config file is describe in the <<fake/../java-adapter-config.adoc#_java_adapter_config,Java adapter configuration>> section.
 
 Next you must set the `auth-method` to `KEYCLOAK` in `web.xml`.
@@ -259,7 +260,9 @@ This metadata is instead defined within server configuration (i.e. `standalone.x
 
 The `secure-deployment` `name` attribute identifies the WAR you want to secure.
 Its value is the `module-name` defined in `web.xml` with `.war` appended.
+
 The rest of the configuration corresponds pretty much one to one with the `keycloak.json` configuration options defined in <<fake/../java-adapter-config.adoc#_java_adapter_config,Java adapter configuration>>.
+
 The exception is the `credential` element. 
 
 To make it easier for you, you can go to the {{book.project.title}} Administration Console and go to the Application/Installation tab of the application this WAR is aligned with.

topics/oidc/java/jetty9-adapter.adoc

@@ -58,6 +58,7 @@ This is a Jetty specific config file and you must define a Keycloak specific aut
 ----
 
 Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
+
 The format of this config file is describe in the <<fake/../java-adapter-config.adoc#_java_adapter_config,Java adapter configuration>>            section.
 
 WARNING: The Jetty 9.1.x adapter will not be able to find the `keycloak.json` file.

topics/oidc/java/tomcat-adapter.adoc

@@ -45,7 +45,8 @@ This is a Tomcat specific config file and you must define a Keycloak specific Va
 ----
 
 Next you must create a `keycloak.json` adapter config file within the `WEB-INF` directory of your WAR.
-The format of this config file is describe in the <<fake/../java-adapter-config.adoc#_java_adapter_config,Java adapter configuration>>            section.
+
+The format of this config file is describe in the <<fake/../java-adapter-config.adoc#_java_adapter_config,Java adapter configuration>>           
 
 Finally you must specify both a `login-config` and use standard servlet security to specify role-base constraints on your URLs.
 Here's an example: 

topics/saml/java/jetty-adapter.adoc

@@ -1,4 +1,5 @@
 [[_jetty_saml_adapter]]
+
 ==== Jetty SAML Adapters
 
 To be able to secure WAR apps deployed on Jetty you must install the {{book.project.name}} Jetty 9.x or 8.x SAML adapter into your Jetty installation.