Merge pull request #615 from bstansberry/pulls

Pulls

_layouts/base.html

@@ -24,8 +24,6 @@
 
     gtag('config', 'UA-40221748-1');
   </script>
-  <script src="{{ site.baseurl }}assets/javascript/tracking.js"></script>
-  <script src="https://design.jboss.org/matomo/matomo.js" async defer></script>
 
   {% if page.link %}
   <meta http-equiv="refresh" content="0; {{ page.link }}">

_posts/2024-05-06-caching-realm-update-of-credentials.adoc

@@ -0,0 +1,11 @@
+---
+layout: post
+title:  'Caching realm now automatically tries to authenticate users with the underlying realm if authentication with cached credentials fails'
+date:   2024-05-06
+tags:   elytron security caching realm credentials authentication
+author: dvilkola
+synopsis: Learn how the Caching Realm can now update outdated credentials.
+link: https://wildfly-security.github.io/wildfly-elytron/blog/caching-security-realm-authenticate-with-underlying-realm-on-failure/
+---
+
+WildFly provides a caching security realm that allows you to cache the results of a credential lookup from a security realm. WildFly 32+ will automatically attempt to verify credentials with the underlying realm if an authentication fails with the cached credentials. If this authentication succeeds, the obsolete credential is replaced with the updated credential. This functionality is useful if the credentials have been updated externally of WildFly.

_posts/2024-05-07-dynamic-client-ssl-context.adoc

@@ -0,0 +1,11 @@
+---
+layout: post
+title:  'Dynamic client SSL context that automatically delegates to different SSLContexts based on the host and port of the peer'
+date:   2024-05-07
+tags:   elytron dynamic client ssl context
+author: dvilkola
+synopsis: Learn about the new Dynamic Client SSL Context feature.
+link: https://wildfly-security.github.io/wildfly-elytron/blog/dynamic-client-ssl-context/
+---
+
+WildFly 32 introduces the ability to configure a dynamic client SSL context. The dynamic client SSL context will dynamically switch between different SSL contexts based on the host and port of the peer. The host and port rules can be specified in the authentication context. This blog post demonstrates how to use this new resource.