Update to Keycloak 11.0.1

README.md

@@ -12,33 +12,31 @@ with existing applications by leveraging Keycloak identity brokering features.
 Keycloak is a nice product, but still lacking on some aspects of SAML2 compatibility,
 and the SPID specifications deviate from the SAML2 standard in some key aspects.
 
-Apart from the SPID-SAML2 protocol differences the main issue that this project works around 
-is Keycloak lack of support for transient identities. Also, some of the SP behaviors 
+Besides the SPID-SAML2 protocol differences, the main issue that this project works around 
+is Keycloak's lack of support for transient identities. Also, some of the SP behaviors 
 are hardcoded to work with simple IdPs only (i.e. the SP metadata generation is 
-severely lacking).
+severely lacking). Keycloak is slowly improving on this aspect, so over time this plugin 
+will become simpler and targeted on implementing only the specific changes required by SPID.
 
 I have documented a reference configuration for SPID and the workarounds required 
-in the project wiki (https://github.com/lscorcia/keycloak-spid-provider/wiki).
-
-Please make sure to read it and understand the config steps and the open issues and
+in the project wiki (https://github.com/lscorcia/keycloak-spid-provider/wiki). Please make 
+sure to read it and understand the config steps and the open issues and
 limitations before planning your Production environment.
 
 ## Status
 This project is still at an alpha stage. It is currently under development 
-and things may change quickly.  
-Also, as far as I know it has not been used in Production in any environment yet.  
-
-It builds and successfully allows login/logout to the SPID-TestEnv2 test IdP 
-(https://github.com/italia/spid-testenv2) and to the online SPID tester 
-(https://idptest.spid.gov.it).  
+and things may change quickly. It builds and successfully allows login/logout 
+to the SPID-TestEnv2 test IdP (https://github.com/italia/spid-testenv2) 
+and to the online SPID tester (https://idptest.spid.gov.it).  
+As far as I know it has not been used in Production in any environment yet.  
 
-Until the project gets to a stable release, it will be targeting a reasonably recent release 
+Until the project gets to a stable release, it will be targeting the most recent release 
 of Keycloak as published on the website (see property `version.keycloak` in file `pom.xml`).
-Currently the main branch is targeting Keycloak 11.0.0, which unfortunately has a couple of 
-important regressions impacting SAML identity brokering, however a point release fixing them
-is coming soon.  
-At the moment, I suggest you to test this package by building the latest available sources 
-for Keycloak yourself and grabbing a couple of extra patches. Detailed instructions are
+Currently the main branch is targeting Keycloak 11.0.1. **Do not use this provider with previous 
+versions of Keycloak, it won't work!**  
+
+If you are evaluating this solution, my suggestion is to test the provider by compiling Keycloak
+yourself using the latest available sources, and grabbing a couple of extra patches. Detailed instructions are
 available in the project wiki (https://github.com/lscorcia/keycloak-spid-provider/wiki/Installing-the-SPID-provider).
 
 ## Build requirements

pom.xml

@@ -16,7 +16,7 @@
     <url>https://github.com/lscorcia/keycloak-spid-provider</url>
 
     <properties>
-        <version.keycloak>11.0.0</version.keycloak>
+        <version.keycloak>11.0.1</version.keycloak>
         <maven.compiler.source>1.8</maven.compiler.source>
         <maven.compiler.target>1.8</maven.compiler.target>
         <failOnMissingWebXml>false</failOnMissingWebXml>
@@ -25,8 +25,8 @@
 
     <scm>
         <developerConnection>scm:git:https://github.com/lscorcia/keycloak-spid-provider.git</developerConnection>
-      <tag>HEAD</tag>
-  </scm>
+        <tag>HEAD</tag>
+    </scm>
 
     <dependencies>
         <dependency>
@@ -74,7 +74,7 @@
         <dependency>
             <groupId>org.slf4j</groupId>
             <artifactId>slf4j-api</artifactId>
-            <version>1.7.21</version>
+            <version>1.7.30</version>
         </dependency>
         <!-- https://mvnrepository.com/artifact/junit/junit -->
         <dependency>