Merge pull request #153 from arjantijms/master

Consistently rename all files to recommended .adoc

spec/src/main/asciidoc/authenticationMechanism.asciidoc → spec/src/main/asciidoc/authenticationMechanism.adoc

@@ -99,7 +99,7 @@ A Jakarta EE container MUST support built-in beans for the following _HttpAuthen
 
 All of these beans MUST have the qualifier @Default and the scope @ApplicationScoped, as defined by the CDI specification.
 
-All of the built-in beans MUST support authentication using _IdentityStore_, described in Chapter 3, "<<identityStore.asciidoc#identity-store,Identity Store>>", but MAY fall-back to container-specific methods if no _IdentityStore_ is available.
+All of the built-in beans MUST support authentication using _IdentityStore_, described in Chapter 3, "<<identityStore.adoc#identity-store,Identity Store>>", but MAY fall-back to container-specific methods if no _IdentityStore_ is available.
 
 See also the "<<Implementation Notes>>" section of this chapter.
 
@@ -301,7 +301,7 @@ Intercepting _cleanSubject()_::
 ** Remove the cookie.
 ** Call the _removeLoginToken()_ method of the _RememberMeIdentityStore_.
 
-See also the description of _RememberMeIdentityStore_ in Chapter 3, "<<identityStore.asciidoc#identity-store,Identity Store>>".
+See also the description of _RememberMeIdentityStore_ in Chapter 3, "<<identityStore.adoc#identity-store,Identity Store>>".
 
 ==== AutoApplySession Annotation
 

spec/src/main/asciidoc/identityStore.asciidoc → spec/src/main/asciidoc/identityStore.adoc

@@ -253,7 +253,7 @@ public interface RememberMeIdentityStore {
 
 _RememberMeIdentityStore_ can only be used when an application includes an _HttpAuthenticationMechanism_ or configures one of the built-in ones. The application must specify the _RememberMe_ annotation on the _HttpAuthenticationMechanism_ to configure the _RememberMeIdentityStore_.
 
-See the description of the _RememberMe_ annotation in Chapter 2, "<<authenticationMechanism.asciidoc#authentication-mechanism,Authentication Mechanism>>".
+See the description of the _RememberMe_ annotation in Chapter 2, "<<authenticationMechanism.adoc#authentication-mechanism,Authentication Mechanism>>".
 
 === Installation and Configuration
 

spec/src/main/asciidoc/security-spec.adoc

@@ -23,18 +23,18 @@ endif::[]
 :sectnums!:
 include::license-efsl.adoc[]
 
-// == Scope
+// == Toc
 :sectnums:
 
-include::preface.asciidoc[]
+include::preface.adoc[]
 
-include::concepts.asciidoc[]
+include::concepts.adoc[]
 
-include::authenticationMechanism.asciidoc[]
+include::authenticationMechanism.adoc[]
 
-include::identityStore.asciidoc[]
+include::identityStore.adoc[]
 
-include::securityContext.asciidoc[]
+include::securityContext.adoc[]
 
-include::bibliography.asciidoc[]
+include::bibliography.adoc[]
 

spec/src/main/asciidoc/securityContext.asciidoc → spec/src/main/asciidoc/securityContext.adoc

@@ -31,7 +31,7 @@ The _getPrincipalsByType()_ method retrieves all principals of the given type. T
 
 Where both a container caller principal and an application caller principal are present, the value returned by _getName()_ MUST be the same for both principals.
 
-See the Chapter 1, "<<concepts.asciidoc#concepts,Concepts>>", for more information on principal handling.
+See the Chapter 1, "<<concepts.adoc#concepts,Concepts>>", for more information on principal handling.
 
 The _isCallerInRole()_ method takes a String argument that represents the role that is to be tested for. It is undefined by this specification how the role determination is made, but the result MUST be the same as if the corresponding container-specific call had been made (i.e., _HttpServletRequest.isUserInRole()_, _EJBContext.isCallerInRole()_), and MUST be consistent with the result implied by other specifications that prescribe role-mapping behavior.