Isode Products

From the Isode blog...

Subscribe to RSS headline updates from:
Powered by FeedBurner

 

 

On this page you can find out about new product functionality and changes in Isode R14.2:

R14.2 is the current Isode release. R14.2 was preceded by R14.1.


M-Link. The first release of our new XMPP Server.

  • High performance & Good Scaling
  • Good interoperability with deployed XMPP & Jabber clients and servers
  • SASL Authentication
  • Very easy to set up
  • SNMP Monitoring following Network Services MIB (RFC 2788)
  • Account configuration held in directory
    • Can use IMA (Internet Messaging Web Administration) with common administration for all Internet services. This will be convenient for Internet Messaging deployments.
    • Can use an existing M-Vault configuration with SASL authentication based on user-id or email address. This will be convenient for M-Vault customers
  • Conformance:
    • Meets & exceeds basic server compliance (XEP 0212)
    • RFC 3920 and RFC 3921 (XMPP Core)
    • draft-saintandre-rfc3920bis-04.txt and draft- saintandre rfc3921bis-04.txt (Updates to core based on implementation experience)
    • XEP 220 - Server dial-back
    • XEP 78 - non-SASL Authentication.
    • XEP 54 - vCard profiles
    • XEP 30 - Service Discovery

For more information on M-Link, please see the product page here. An evaluation guide for M-Link can be found here.

HF Radio Support

  • STANAG 5066 Subnet Interface Sublayer (SIS) protocol client library, including UDOP (Unreliable Datagram Oriented Protocol) support. STANAG 5066 (Profile for High Frequency (HF) Radio Data Communications) is the NATO standard for data communication over HF Radio. The SIS client protocol allows applications to communicate over TCP with a STANAG 5066 server associated with a modem. This library will enable Isode applications to run directly over STANAG 5066.
  • STANAG 4406 Annex E and ACP 142 operation over STANAG 5066. This provides an alternative to operation over IP, which is expected to provide significant performance improvements by more effective utilization of the HF Radio.

Preview release of Security Labels and Clearances in M-Vault.

The goal of this work is to enable Isode customers to understand capabilities and potential in this area, and to give feedback to Isode on requirements. This functionality may be useful for some basic deployments as provided, although many customers will need additional functionality planned for future releases. Capabilities include:

  • Ability to specify a user's clearance as an attribute in the user's directory entry.
  • Ability to specify Security Labels. Security Labels may be associated with:
    • An individual entry
    • A subtree of the DIT (administrative area specified in a subentry)
    • The whole M-Vault DSA
  • Directory Access Control using Security Labels in addition to basic and simple ACI
  • Control of access to information based on clearance of client (DUA) and
    appropriate label
  • Sodium can display security labels and clearances, and load from
    supplied files

DSI (Directory Services Interface) web interface to directory:

Web interface to directory available separately as a part of M-Vault, as well as within IMA. This provides an independent Web interface onto M-Vault. There are three UI components:

  • Directory search, including vCard and detailed display
  • Phone book (simple display)
  • PIA (Personal Information Administration)

Configurable choice of attributes and information available for searching, entry and display. PIA for Directory provides:

  • Modification of selected entries
  • Password changing (including password policy support)
  • Group display and management
  • Directory search

Password Policy. M-Vault Server enhancements:

  • Ability to lock (disable) accounts
  • Password history controlled by age (rather than number of changes) so that repeated changes cannot clear history
  • Specific accounts can be excluded from password policy. This may be useful to handle special accounts
  • Automatic hash migration on subsequent authentication, so that if the chosen password hashing algorithm is changed, the stored value will be updated when the user next authenticates
  • Web Application Enhancement: Enhancements to IMA (Internet Messaging Administration), PIA (Personal Information Administration) and DSI (Directory Services Interface):
    • Provide feedback on password quality errors (e.g., password too short) when changing password
    • Show password policy password warnings and errors (e.g.,"password expires in 2 weeks") when authenticating.

M-Switch Configuration

Message configuration management is being moved from EMMA (which we plan to replace) to Message Console. R14.2 Message Console contains some core elements of configuration management, accessible from the "Switch View". This enables MTA and Channel configuration to be viewed in the context of operational status.

Message Console

  • The Event Viewer (now a part of Message Console) has a number of usability and scaling enhancements
  • Improved alert handling in delivery reports view


Sodium Sync

  • Sodium Sync Server is added, which will perform scheduled updates independent of the GUI.
  • Ability to change the RDN of leaf entries to a value from the entry being synchronized. This can be useful where the style of naming needs to be changed between directories to a value derived from the entry being synchronized.
  • Ability to "flatten" the DIT on synchronization by removing non-leaf entries of a specified object class.
  • Loading by Synchronization from LDIF. Where a full directory load is needed at intervals, LDIF can be generated and Sodium Sync will determine changes relative to the live directory and then make modifications. This approach is often preferable to "delete and replace", and also enables additional attributes to be added to the live directory.
  • Output synchronization changes to LDIF.
  • Apply changes from change LDIF
  • Compare two LDIFs to generate a change LDIF
  • Compare two directory sub-trees and generate a delta as LDIF. This can be useful for comparing two similar directories.

Sodium

  • New "enumerated" editor functionality
  • Display operational attributes
  • GeneralizedTime display and editing
  • Support for cross-certificates, providing display of cross certificates, and ability to edit both the component certificates and the complete cross certificate value.

Directory Client API

  • Support for password policy LDAP Controls
  • Support for SASL on bind

X.400 APIs

We have an ongoing project to extend our X.400 APIs, and R14.2 will include additional capabilites.

  • Support of X.411 (Message Envelope) features. This part of the project is almost complete. This work includes:
    • Support in X.400 Gateway API
    • Support for relevant features in X.400 P3/P7 'C' Client APIs
  • Support of P772 (STANAG 4406) Military Messaging features. We expect to include some, but not all of the planned features.
  • Extension of P7 "list" API, so that it can handle size limit and ranges. This will enable efficient listing of very large mailboxes.

Anti-Spam

  • Support for SURBL, that provides real time matching of URLs in messages (and is very effective).

M-Switch SMTP

  • Sub-addressing support. If there is a local user "joe@myorg.com", this means that messages addressed to joe+XXXX@myorg.com will be delivered (by LMTP or SMTP) as if to joe@myorg.com. This additional information may be used by M-Box to control SIEVE processing on message delivery, or for other purposes.

M-Box

  • "Global" SIEVE scripts, so that delivery time processing can be defined for all messages (e.g., to use a message annotation or sub-addressing to file a message in a Junk/ folder).
  • Message cleanout, so that old messages may be automatically deleted on the server

Platform Support Changes

  • GUIs and client components supported on Windows Vista
  • Servers will run in Windows Vista for demonstration and other non-production purposes

 

 
Copyright © 2008 Isode privacy   feedback Subscribe to our rss newsfeed