// 4.x
+AuthProvider authProvider = ...
+
+// 5.0
+AuthenticationProvider authProvider = ...Vert.x Logging API usage has been reduced in Vert.x 4 to be used by Vert.x components, in other words +the API has become internal to Vert.x:
+io.vertx.core.logging.Logger and io.vertx.core.logging.LoggerFactory have been deprecated to discourage usage of this API. Instead, a logging API should be used such as Log4j 2 or SLF4J.
Of course, configuration of the Vert.x logging back-end remains fully supported as usual, like the vertx.logger-delegate-factory-class-name system property.
A few system properties have been removed in Vert.x 5.
@@ -1557,6 +1582,26 @@io.vertx.ext.auth.AuthProvider` has been deprecated in Vert.x 4.0 in favour of io.vertx.ext.auth.authentication.AuthenticationProvider.
// 4.x
+AuthProvider authProvider = ...
+
+// 5.0
+AuthenticationProvider authProvider = ...User related operations have been moved under a single context API accessible from RoutingContext
// 4.x
+routingContext.clearUser();
+
+// 5.0
+UserContext userContext = routingContext.userContext();
+userContext.logout();The RoutingContext#setUser method has been removed, this operation should be performed by authentication handlers instead.
StaticHandler methods setAllowRootFileSystemAccess and setWebRoot are removed after deprecation in Vert.x 4.
StaticHandler methods setAllowRootFileSystemAccess and setWebRoot are removed after deprecation in Vert.x 4.x.
Instead, the handler must be configured at creation time:
+// 4.x
+StaticHandler handler = StaticHandler.create().setAllowRootFileSystemAccess(true).setWebRoot(root);
+
+// 5.0
+StaticHandler handler = StaticHandler.create(FileSystemAccess.ROOT, root);