Merge pull request wso2#1 from wso2/testhackathon

Testhackathon
ayshsandu · Sep 17, 2019 · f6aae01 · f6aae01
2 parents f60e267 + 7aec443
commit f6aae01
Show file tree

Hide file tree

Showing 13 changed files with 12 additions and 15 deletions.
diff --git a/en/docs/assets/img/getting-started/authentication-in-non-sso.png b/en/docs/assets/img/getting-started/authentication-in-non-sso.png
diff --git a/en/docs/assets/img/getting-started/authentication-in-sso.png b/en/docs/assets/img/getting-started/authentication-in-sso.png
diff --git a/en/docs/assets/img/getting-started/carbon-attribute-finder.png b/en/docs/assets/img/getting-started/carbon-attribute-finder.png
diff --git a/en/docs/assets/img/getting-started/carbon-policy-finder.png b/en/docs/assets/img/getting-started/carbon-policy-finder.png
diff --git a/en/docs/assets/img/getting-started/saml-authentication-flow.png b/en/docs/assets/img/getting-started/saml-authentication-flow.png
diff --git a/en/docs/assets/img/getting-started/types-of-access-control.png b/en/docs/assets/img/getting-started/types-of-access-control.png
diff --git a/en/docs/assets/img/getting-started/xacml-engine-architecture.png b/en/docs/assets/img/getting-started/xacml-engine-architecture.png
diff --git a/en/docs/assets/img/getting-started/xacml-system-architecture.png b/en/docs/assets/img/getting-started/xacml-system-architecture.png
diff --git a/en/docs/get-started/access-control-and-entitlement-management.md b/en/docs/get-started/access-control-and-entitlement-management.md
@@ -97,7 +97,7 @@ applications.
 !!! Info "Recommended reading"
     For more information on XACML specifications and other related
     information, see [the OASIS 
-    website](http://oasis-open.org/committees/xacml rel="noopener").
+    website](http://oasis-open.org/committees/xacml "(target|_blank)").
 
 
 

diff --git a/en/docs/learn/openid-connect-logout-url-redirection.md b/en/docs/learn/openid-connect-logout-url-redirection.md
@@ -81,7 +81,7 @@ Follow the steps below to send an OIDC logout request:
     ```
 
     Following are the parameters you need to specify in the URL:
-
+    <a name="parameters"></a>
     <table>
     <thead>
     <tr class="header">
@@ -157,9 +157,7 @@ when you send an OIDC logout request as a POST request:
 ```
 
 For descriptions of all the parameters that you need to specify in the
-POST request, see the [parameter descriptions given
-above](#OpenIDConnectLogoutURLRedirection-parameters).
-
+POST request, see the <a href="<#parameters>parameter descriptions given above</a>
 Following is the sample HTML form with sample parameter values to render
 the page in a browser:
 

diff --git a/en/docs/learn/password-history-validation.md b/en/docs/learn/password-history-validation.md
@@ -24,12 +24,11 @@ password. Follow the steps below to configure the count.
         configure the password policy. Next, logout and login again with
         Tenant B credentials to configure a different policy for Tenant B.
 
-
 
     ![password-history-validation](../../assets/img/using-wso2-identity-server/password-history-validation.png) 
 
 !!! info "Related Links"
 
-    See [Configuring
-    Claims](../../learn/configuring-claims) for more
-    information on how to store the claim values in the user store.
+    By default, the claim values of the identity claims used in this feature are stored in 
+    the JDBC datasource based on a configuration. See [Configuring Claims](../../learn/configuring-claims) 
+    for more information on how to store the claim values in the user store.
diff --git a/en/docs/learn/password-patterns.md b/en/docs/learn/password-patterns.md
@@ -1,6 +1,6 @@
 # Password Patterns
 
-WSO2 Identity Server (IS) allows you to define custom password policies
+WSO2 Identity Server allows you to define custom password policies
 and enforce them at the point of user creation. This topic guides you
 through configuring a simple custom password policy and enforcing it.
 You can also have a different password policy for each tenant in a
@@ -13,8 +13,11 @@ multi-tenant environment.
 3.  Expand the **Password Policies** tab.
 4.  Expand the **Password Patterns** tab and select **Enable Password
     Policy Feature**. Update the default values and click **Update**.
+
+ ![password-policies](../../assets/img/using-wso2-identity-server/password-policies.png) 
+
 
-    !!! note "Configuring password policies for multiple tenants"
+   !!! note "Configuring password policies for multiple tenants"
         To configure this separately for different tenants in a
         multi-tenant environment, first login with Tenant A credentials and
         configure the password policy. Next, logout and login again with
@@ -60,8 +63,6 @@ multi-tenant environment.
     </tbody>
     </table>
 
-    ![password-policies](../../assets/img/using-wso2-identity-server/password-policies.png) 
-
 !!! info "Related Links"
 
     -   To configure a global password policy that applies to all tenants,

diff --git a/en/mkdocs.yml b/en/mkdocs.yml
@@ -63,7 +63,7 @@ nav:
     - 'General Data Protection Regulation': compliance/general-data-protection-regulation.md
     - 'Electronic Identification, Authentication and Trust Services Regulation': compliance/electronic-identification-authentication-and-trust-services-regulation.md
   - 'Learn':
-    - 'learn':
+    - 'Tutorials':
       - 'Authentication':
         - 'Logging in to your application via Identity Server using Facebook Credentials': learn/logging-in-to-your-application-via-identity-server-using-facebook-credentials.md
         - 'Configuring Shibboleth IdP as a Trusted Identity Provider': learn/configuring-shibboleth-idp-as-a-trusted-identity-provider.md
@@ -274,7 +274,6 @@ nav:
           - 'Forced Password Reset': learn/forced-password-reset.md
           - 'User Account Suspension': learn/user-account-suspension.md
         - 'Password Policies':
-          - 'Password Policies': learn/password-policies.md
           - 'Password History Validation': learn/password-history-validation.md
           - 'Password Patterns': learn/password-patterns.md
         - 'Login Policies':