dependabot[bot] opened a new pull request, #28934: URL: https://github.com/apache/camel/pull/28934
Bumps [io.rest-assured:rest-assured](https://github.com/rest-assured/rest-assured) from 6.2.0 to 6.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rest-assured/rest-assured/blob/master/changelog.txt";>io.rest-assured:rest-assured's changelog</a>.</em></p> <blockquote> <h2>Changelog 6.3.0 (2026-10-23)</h2> <ul> <li>Fix form authentication sending the request for the CSRF token page, the request that follows a 302 of the login page and the login request with the static RestAssured settings only, so a proxy, an SSL setting such as relaxedHTTPSValidation() or a keystore, or a config(..) set on the request (or in a request specification) wasn't used for them. They are now sent with the config and the proxy of the request, like the request for the login page already was (issue <a href="https://redirect.github.com/rest-assured/rest-assured/issues/1965";>#1965</a>) (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2010";>#2010</a>) (thanks to Obrams for PR)</li> <li>Fix form authentication sending the cookies set by the login page response to whatever host the 302 of a non-GET login page request pointed to. Like a browser, it only sends them when the redirect goes to the same host. The Location header is now also resolved against the URL of the login page, so a relative Location is followed on the host of the login page (issue <a href="https://redirect.github.com/rest-assured/rest-assured/issues/1965";>#1965</a>) (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2010";>#2010</a>) (thanks to Obrams for PR)</li> <li>Added SSLConfig.sslContext(SSLContext) and hostnameVerifier(HostnameVerifier), with getSSLContext() and getHostnameVerifier(), the same on CertificateAuthSettings, and the matching properties on CertAuthScheme. They take the JDK's javax.net.ssl types and replace sslSocketFactory(..), x509HostnameVerifier(..) and their getters, which take Apache HttpClient 4 types and are now deprecated, since HttpClient 4 types leave the API in REST Assured 7.0.0. Host names are still verified strictly by default when you set an SSLContext</li> <li>Added HttpClientConfig.connectTimeout(Duration), readTimeout(Duration), connectionRequestTimeout(Duration), keepResponseCookies(boolean), cookieDatePatterns(String...) and expectContinue(boolean), with getters, as replacements for the HttpClient 4 parameters http.connection.timeout, http.socket.timeout, http.conn-manager.timeout, http.protocol.cookie-policy, http.protocol.cookie-datepatterns and http.protocol.expect-continue. The parameter methods (the HttpClientConfig(Map) constructor, params(), setParam, withParams, setParams and addParams) are deprecated and will be removed in REST Assured 8.0.0</li> <li>Added RedirectConfig.followRedirectsForAllMethods(boolean) and followsRedirectsForAllMethods(). It follows redirects of POST, PUT, DELETE and other requests too. Use it instead of installing HttpClient 4's LaxRedirectStrategy through an HttpClientFactory</li> <li>Added REST Assured's own MultipartMode enum with HttpClientConfig.multipartMode(MultipartMode) and multipartMode(), replacing httpMultipartMode(HttpMultipartMode) and httpMultipartMode(), which are now deprecated</li> <li>Added CookieFilter.getCookies(), which returns the stored cookies as REST Assured Cookies, and CookieFilter.addCookie(Cookie), replacing getCookieStore(), which is now deprecated together with extractEffectiveUriFromContext(..)</li> <li>Deprecated HttpClientConfig.HttpClientFactory, httpClientFactory(..) and httpClientInstance(), and QueryableRequestSpecification.getHttpClient(), since HttpClient 4 types leave the API in REST Assured 7.0.0. REST Assured 7.0.0 adds customizeClient(..) to customize the HTTP client</li> <li>Added AuthenticationContext, AuthenticationScheme.authenticate(AuthenticationContext) and ContextAuthenticationScheme, so that a custom authentication scheme can set headers, answer Basic, Digest and NTLM challenges, sign with OAuth and use a client certificate without depending on HttpClient 4. Implement ContextAuthenticationScheme instead of AuthenticationScheme.authenticate(HTTPBuilder), which is now deprecated, since HTTPBuilder exposes HttpClient 4 and is removed in REST Assured 7.0.0</li> <li>Added the object mapper factory interfaces and their defaults (GsonObjectMapperFactory, Jackson2ObjectMapperFactory, Jackson3ObjectMapperFactory, JohnzonObjectMapperFactory, JsonbObjectMapperFactory, JAXBObjectMapperFactory and JakartaEEObjectMapperFactory, and DefaultGsonObjectMapperFactory and so on) to rest-assured-common in the package io.restassured.common.mapper.factory, and NumberReturnType to io.restassured.common.config. ObjectMapperConfig, JsonPathConfig, XmlPathConfig, JsonConfig, JsonPath.using(..) and XmlPath.using(..) accept them, and JsonConfig.DEFAULT_NUMBER_LENGTH_LIMIT is added. The old types in io.restassured.path.json.mapper.factory, io.restassured.path.xml.mapper.factory and JsonPathConfig.NumberReturnType are deprecated. The old factory types extend the new ones, so existing code keeps working. They're removed in REST Assured 8.0.0. Passing null to numberReturnType(..), new JsonConfig(..) or new JsonPathConfig(..) is now ambiguous and needs a cast</li> <li>Non-backward compatible change: in Groovy 4 (but not Groovy 5), passing a closure directly to a factory setter such as ObjectMapperConfig.jackson2ObjectMapperFactory { type, charset -> .. } now fails with "Ambiguous method overloading", since the setters take both the old and the new factory type. Cast the closure to the factory type, for example jackson2ObjectMapperFactory({ type, charset -> .. } as Jackson2ObjectMapperFactory)</li> <li>Deprecated the Jackson 1 object mapper factory setters (ObjectMapperConfig.jackson1ObjectMapperFactory(..), JsonPathConfig.jackson1ObjectMapperFactory(..) and JsonPath.using(Jackson1ObjectMapperFactory)), since Jackson 1 support is removed in REST Assured 7.0.0</li> <li>rest-assured-common now has optional dependencies on the JSON and XML mappers its factories use (Jackson 2 and 3, Gson, Johnzon, Yasson, JSON-B, JAXB and Jakarta XML Binding). They are optional, so nothing new ends up on your classpath</li> <li>REST Assured, RestAssuredMockMvc and RestAssuredWebTestClient now fail with an IllegalStateException that explains how to align the versions when an older rest-assured-common is on the classpath (for example one pinned by the Spring Boot 3 dependency management), instead of a NoClassDefFoundError</li> <li>Published json-path-gpath and xml-path-gpath, the REST Assured 7.0.0 names of json-path and xml-path. In 6.x they are relocation poms that resolve to json-path and xml-path at the same version, so you can switch your build to the new names before upgrading. They are also in rest-assured-bom</li> <li>Added the rest-assured-openrewrite module with the OpenRewrite recipe io.restassured.MigrateRestAssured6Deprecations, which moves Java code from the APIs deprecated in this version to their replacements: the object mapper factories and NumberReturnType in rest-assured-common, hostnameVerifier(..), multipartMode(..), and the HttpClientConfig settings that replace setParam(..) for the timeouts, the "ignoreCookies" and "default" cookie policies and expect-continue. It also marks subclasses of REST Assured's authentication schemes that only override authenticate(HTTPBuilder), which REST Assured 7.0.0 no longer calls. Run it with the rewrite-maven-plugin or the OpenRewrite Gradle plugin, with io.rest-assured:rest-assured-openrewrite as recipe dependency</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rest-assured/rest-assured/commit/b2fa63a974f79298290a3877f7d34416cac67d13";><code>b2fa63a</code></a> [maven-release-plugin] prepare release rest-assured-6.3.0</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/9bee82bead83bac08fec1be99e6739d954e2c7f1";><code>9bee82b</code></a> [ci skip] Preparing changelog for release</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/6511a840d7c91aaad7077edab973235849807472";><code>6511a84</code></a> [ci skip] Updated changelog to reflect the latest changes</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/d1266d6317a50a48a36647a860fe66c7d2d22ca5";><code>d1266d6</code></a> Send the extra requests of form authentication with the config and proxy of t...</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/0639bb37fc1581d80ccd1d8ad5b2fbf46e7708cd";><code>0639bb3</code></a> Stop PathParamITest from calling google.se (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/1995";>#1995</a>)</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/5de3595f769cd6e676d41c31ef75bae468c6186d";><code>5de3595</code></a> Stop SSLITest from calling duckduckgo.com (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2009";>#2009</a>)</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/9078ee01430e0024cc4538ee58819558d810acec";><code>9078ee0</code></a> Fix issues found in the review of the 6.3.0 changes (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2008";>#2008</a>)</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/91576d5a5da5c175357b03df0f867e4a2729f23c";><code>91576d5</code></a> Compile with maven.compiler.release=17 and run CI on JDK 17, 21 and 25 (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2007";>#2007</a>)</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/6cc8d43bc5e25ecfe39fe8e69a01d223b79d2cb1";><code>6cc8d43</code></a> Add rest-assured-openrewrite with the MigrateRestAssured6Deprecations recipe ...</li> <li><a href="https://github.com/rest-assured/rest-assured/commit/d35f1ca9608651840ba92454dd4d9c3c2bc6b894";><code>d35f1ca</code></a> Publish json-path-gpath and xml-path-gpath as relocation poms (<a href="https://redirect.github.com/rest-assured/rest-assured/issues/2005";>#2005</a>)</li> <li>Additional commits viewable in <a href="https://github.com/rest-assured/rest-assured/compare/rest-assured-6.2.0...rest-assured-6.3.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
