Social and Email Authentication
There are several strategies to choose from when it comes to user authentication. Login methods can be enabled or disabled for both the Coral Admin and the Comment Stream separately thus allowing you to use different methods for different user groups.
You can also use “Allow Registration” to restrict or allow users that have not signed up before to register and create new user accounts.
To configure authentication for your instance of Coral, go to Configure > Authentication.
Best when you want Coral to manage all user registration, creation and authentication. Requires the least amount of setup and configuration. Users register by creating a Username (must be unique across users, no spaces or special chars), Email, and Password. All user details are stored in Coral’s database.
By Default - users are sent a verification email and are prompted to verify email addresss, however completing the email verification step is not required to submit comments.
Allows integration with your existing OpenID Connect authentication provider. When enabled this strategy adds a “Login with ___”, button to Coral’s login modal with the value you’ve specified for
With OpenID Connect authentication is handled by passing an access token parameter to the comment stream embed when placing the call to render it. To learn more please visit: https://openid.net/connect/
When you want users to authenticate via your existing identity system, and be automatically registered/logged into Coral. Users register, login, and manage their user details on your existing site, your user database maintains the source of truth for all user information. Users are created and updated in Coral via jwt tokens passed from your auth service to Coral.
Requires advanced configuration, please see: Single Sign On
Allows users to use existing social media account to sign in. Requires you to setup API keys with social sign on provider, and configure your API keys in Coral.
Users register and login via a “Sign in with ….”, and are not required to set a password if Email based authentication is not enabled. Users with social accounts are prompted to associate an email address with their social profile to enable notifications.
Optional features you can enable or disable to allows users to:
- change their usernames (once every 14 days)
- download their comments
- delete their account details.
Determines length of user sessions when not using SSO or when
exp claim is not provided on jwt. Default:
Coral usernames are subject to the following validations:
- USERNAME_REGEX =
- USERNAME_MAX_LENGTH =
- USERNAME_MIN_LENGTH =
NOTE: SSO users are not subject to username restricitons