Email Providers

The task of sending email messages is used in different places, like when registering a new account, or using the Email authenticator. Email is normally sent through an SMTP server, that takes responsibility of delivering the email at the recipient’s mailbox. It is however also possible to use alternative email delivery services when using the Curity Identity Server.

An email provider is a pluggable component in Curity. By default, an SMTP-based email provider plugin is included with the server. An email provider is configured as a server facility, and therefore an email provider can be easily shared among multiple parts of the server configuration. Each configured service is able to configure its own email provider from the server’s facilities, allowing for easy default configuration of sending out emails in a standard way.

This section will describe how to configure the included SMTP email provider. Alternatively, it is possible to implement your own pluggable email provider through the Email Provider extension point, which is described in more detail in the developer’s guide.

SMTP Email Provider

The most common way to send out email messages, is through the SMTP protocol. To do this, the following configuration settings are available:

  1. SMTP server name
  2. The port of the SMTP server; defaults to 587
  3. Whether to use a TLS-protected connection to communicate with the server
  4. An email-address that is used as the sender of each outgoing email message
  5. Optionally, a username and password to use to authenticate with the SMTP server

These settings must be used to configure Smtp in the facilities section.


Fig. 32 Configuring an Email facility in the Admin UI of Curity

Configure Email Provider for a Service

There is a system wide setting to indicate which email provider should be used by default. This setting is configured on the System’s General page.


Fig. 33 Setting up the default email provider