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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, Search username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Address Federation 16 Highlights: Broker plugin support. Support interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Versions 16 Full release notes. Highlights: Broker plugin support. Support Netty interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When

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 Netty native epoll interpreted as an LDAP search filter, where the LDAP search filter syntax is defined by the IETF standard, RFC 2254. A short introduction to the search filter syntax is available from Oracle's JNDI tutorial, username is mapped to a subject DN, encoded as a string (where the string encoding is specified by RFC 2253). For example, the system username is mapped to the CN=system,O=Progress,C=US subject DN. When