This article explains how to configure and automate the Everbridge app login process using Windows Registry keys or MSI parameters. It covers methods for prepopulating the organization code, username, and password, and Single Sign-On (SSO) flow — either through the default browser or within the app.
Organisation Code
Setting the orgCode via the Windows Registry or as an MSI parameter will prepopulate the organization code and skip the initial screen.
Depending on your organization’s configuration, this will either display a screen for entering a username and password or a link to your Single Sign-On login page.
Username and Password
Setting the username and password via the Windows Registry will prepopulate the login fields and skip the login screen.
This can be combined with forceStartInTray to automatically log in to the app and keep it hidden in the system tray, preventing interruptions for the user.
Single Sign-On
The Single Sign-On page can be automatically opened in the default browser by using the isSSO registry key.
In-App Single Sign-On
The Single Sign-On page can be opened within the app instead of the default browser by using useInAppBrowserForSSO via the Windows Registry or as an MSI parameter.
If your SSO provider does not require user interaction, this page can automatically log the user in. In this case, you can use hideInAppBrowserForSSO and forceStartInTray (via the Windows Registry or MSI parameter) to automatically log in and keep the app minimized in the system tray to avoid interrupting the user.
Article Feedback
While we can’t respond to you directly, we’d love to know how we can improve the article.
Article is closed for comments.