Spring Security Shiro Plugin - Reference Documentation Burt Beckwith Version 3.1.2.BUILD-SNAPSHOT Table of Contents 1. Introduction to the Spring Security Shiro Plugin . . . . . . . . . . . . . . Chapter 1. Introduction to the Spring Security Shiro Plugin The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring Security and Shiro. It currently only supports supports Shiro ACLs, since Spring Security ACLs are very powerful but can be very cumbersome to use, and the Shiro approach is straightforward and simple. The majority of the authentication and authorization

1 Shiro support for the Spring Security plugin Table of contents 2 Shiro support for the Spring Security plugin - Reference Documentation Authors: Burt Beckwith Version: 0.1 Table of Contents 1 Introduction The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring Security and . It currently only supports Shiro ACLs, since Spring Security ACLs are very Shiro authentication and authorization work is still done by Spring Security. This plugin listens for Spring Security authentication events and uses the Spring Security Authentication instance to build and register a Shiro

the Spring Security plugin Shiro support for the Spring Security plugin - Reference Documentation Authors: Burt Beckwith Version: 1.0.0 Table of Contents 1 Introduction to the Spring Security Shiro Plugin Spring Security Shiro Plugin The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring and . It currently only supports Shiro ACLs, since Spring Security ACLs are are very Security Shiro powerful but can be very cumbersome to use, and the Shiro approach is straightforward and simple. The majority of the authentication and authorization work is still done by Spring

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Failover Diverting subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They will

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They will

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Failover Diverting subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They will

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session subscriber using CleanSession=1 is now non-durable rather than durable. This may impact security-settings for MQTT clients which previously only had createDurableQueue for their role. They will

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- middle attacks). Enabling it by default aligns core client behavior

Project Info Versions Messaging Concepts Architecture Using the Server Upgrading Address Model Settings Protocols and Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping Message Grouping Consumer Priority Extra Acknowledge Modes Management Management Console Metrics Security Masking Passwords Broker Plugins Resource Limits The JMS Bridge Client Reconnection and Session cluster nodes. Although this is a "breaking" change, not performing hostname verification is a security risk (e.g. due to man-in-the- Versions 10 middle attacks). Enabling it by default aligns core