DefaultPasswordService hashService=org.apache.shiro.crypto.hash.DefaultHashService passwordService.hashService=$hashService hashFormat=org.apache.shiro.crypto.hash.format.Shiro1CryptFormat passwordService passwordService.hashFormat=$hashFormat hashFormatFactory=org.apache.shiro.crypto.hash.format.DefaultHashFormatFactory passwordService.hashFormatFactory=$hashFormatFactory passwordMatcher=org.apache.shiro.authc sslProtocol="TLS" /> -->

0 码力 | 219 页 | 4.16 MB | 10 月前

3

with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is the authorization feature. To require the presence of an incoming certificate (by default, the SSL/TLS layer is configured to treat the presence of a client certificate as optional). The JAAS certificate authentication is supported using the GSSAPI SASL mechanism. With SASL doing Kerberos authentication, TLS can be used to provide integrity and confidentially to the communications channel in the normal way

with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is the authorization feature. To require the presence of an incoming certificate (by default, the SSL/TLS layer is configured to treat the presence of a client certificate as optional). The JAAS certificate authentication is supported using the GSSAPI SASL mechanism. With SASL doing Kerberos authentication, TLS can be used to provide integrity and confidentially to the communications channel in the normal way

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through the Configuring Transports 131 JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. Configuring Netty HTTP Netty HTTP tunnels packets over the with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a regular with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a regular with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a regular with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is