Email Providers

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 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.

Use Cases#

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.

Getting Started#

This section describes how to configure an email provider.

Start by creating an Email Provider under the Facilities menu in the Admin UI by giving it a unique name. Then depending on the type chosen customize its settings.

Currently two Email provider types are supported. SMTP and REST . To allow customization flexibility, Curity provides a REST API towards which the organization can build a small Mailer REST service. This allows an organization to integrate against any Email provider without having to extend the functionality of Curity in a simple manner. 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.

Configure Email Provider for a Service#

There is a zone wide setting to indicate which email provider should be used by default for the given zone. This setting is managed in

For more information on how to further customize the Email system see the developer guide .