v1.0.0, update readme and changelog

privacyidea · Nov 5, 2021 · d205a4f · d205a4f
1 parent 163fd4f
commit d205a4f
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 5 deletions.
diff --git a/Changelog.md b/Changelog.md
@@ -1,5 +1,10 @@
 # Changelog
 
+### v1.0.0 - 2021-11-06
+
+* Support for different configurations in different keycloak realms
+* U2F
+
 ### v0.6 - 2021-04-03
 
 * WebAuthn support

diff --git a/README.md b/README.md
@@ -3,26 +3,26 @@
 # privacyIDEA provider for Keycloak
 
 This provider allows you to use privacyIDEA's 2FA with Keycloak.  
-We added a detailed how to in our [blog](https://community.privacyidea.org/t/how-to-use-keycloak-with-privacyidea/1132).  
-In the blog entry, you can find an example with Keycloak, privacyIDEA and Drupal.
+We added a detailed how-to on our [blog](https://community.privacyidea.org/t/how-to-use-keycloak-with-privacyidea/1132).  
+There you can find an example with Keycloak, privacyIDEA and Drupal.
 
 ## Download
 
 * Check our latest [releases](https://github.com/privacyidea/keycloak-provider/releases).
-* Download the assets privacyIDEA.jar and optionally privacyIDEA.ftl.
+* Download PrivacyIDEA-Provider.jar
 
 ## Installation
 
 * Move the packed jar file into your deployment directory `standalone/deployment`.  
-* Move the template privacyIDEA.ftl to `themes/base/login`. 
+* Optional: Move the template privacyIDEA.ftl to `themes/base/login`. 
 NOTE: For releases from version 0.6 onward, the template will be deployed automatically, so this step can be skipped.
 
 Now you can enable the execution for your auth flow.  
 If you set the execution as 'required', every user needs to login with a second factor.
 
 ## Configuration
 
-You can find different parameters on the configuration page. Those are explained in the following:
+The different configuration parameters that are available on the configuration page of the execution are explained in the following table:
 
 | Configuration | Explanation |
 | ----- | ----- |