Add AuthorizationManager to Messaging
Closes gh-11076
This commit is contained in:
@@ -38,6 +38,12 @@ If not specified, Spring Security will automatically integrate with the messagin
|
||||
* **same-origin-disabled** Disables the requirement for CSRF token to be present in the Stomp headers (default false).
|
||||
Changing the default is useful if it is necessary to allow other origins to make SockJS connections.
|
||||
|
||||
[[nsa-websocket-message-broker-authorization-manager-ref]]
|
||||
* **authorization-manager-ref** Use this `AuthorizationManager` instance; when set, `use-authorization-manager` is ignored and assumed to be `true`
|
||||
|
||||
[[nsa-websocket-message-broker-use-authorization-manager]]
|
||||
* **use-authorization-manager** Uses legacy `SecurityMetadataSource` API instead of `AuthorizationManager` API (default false).
|
||||
|
||||
[[nsa-websocket-message-broker-children]]
|
||||
=== Child Elements of <websocket-message-broker>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user