From b15e32a943ae269c1c7dae4b2084e2ad87f3940d Mon Sep 17 00:00:00 2001 From: Alex Rudyy Date: Wed, 15 Apr 2015 10:00:55 +0000 Subject: QPID-6481: Move java broker docbook into java source tree git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1673703 13f79535-47bb-0310-9956-ffa450edef68 --- ...va-Broker-Security-Authentication-Providers.xml | 51 ---------------------- 1 file changed, 51 deletions(-) delete mode 100644 qpid/doc/book/src/java-broker/security/Java-Broker-Security-Authentication-Providers.xml (limited to 'qpid/doc/book/src/java-broker/security/Java-Broker-Security-Authentication-Providers.xml') diff --git a/qpid/doc/book/src/java-broker/security/Java-Broker-Security-Authentication-Providers.xml b/qpid/doc/book/src/java-broker/security/Java-Broker-Security-Authentication-Providers.xml deleted file mode 100644 index b5546ffebf..0000000000 --- a/qpid/doc/book/src/java-broker/security/Java-Broker-Security-Authentication-Providers.xml +++ /dev/null @@ -1,51 +0,0 @@ - - - - -
- Authentication Providers - - In order to successfully establish a connection to the Java Broker, the connection must be - authenticated. The Java Broker supports a number of different authentication schemes, each with - its own "authentication provider". Any number of Authentication Providers can be configured on - the Broker at the same time. - - - Only unused Authentication Provider can be deleted. For delete requests attempting to - delete Authentication Provider associated with the Ports, the errors will be returned and - delete operations will be aborted. It is possible to change the Authentication Provider on - Port at runtime. However, the Broker restart is required for changes on Port to take effect. - - - - - - - - - - - - -
- -- cgit v1.2.1