Account Activation & Logging In

• Single set of credentials for all your Juvare solutions, such as production and non-production instances of WebEOC, DesignStudio, Unified Command Platform, eICS, EMResource, EMTrack, CORES HAN, Crisis Track, and Juvare Ideas.

• Support for your organization's single sign-on (SSO) through various Identity Providers (IdPs) or Active Directory, allowing you to connect Juvare solutions to your SSO.

• Support for multifactor authentication (MFA) through the Okta Verify and Google Authenticator apps.

Basic requirements and suggestions for using Juvare solutions are provided on the Hosted Requirements pages. One item that is especially important is allowlisting for the given email domains.

It is your Client Administrator’s responsibility to share this information with your IT Department so they can make the necessary updates.

Stakeholders

When implementing Juvare solutions, it is important to consider the implications for other stakeholders already using Juvare solutions. For example, within your organization, your Emergency Department may use Juvare’s EMResource. In this case, if you deploy another Juvare solution that includes Juvare Login Services with SSO, it may affect those users as well.

Your organization may have individuals with access to other Juvare solutions through other subscriptions. Your organization's SSO would still apply to those individuals, as all users are authenticated through Juvare Login Services.

Some IT departments may enforce security restrictions, such as a user being added to an IdP Security Group, as part of their SSO implementation. This could cause confusion and login errors. Juvare does not recommend these additional restrictions, as the team that implements and administers the SSO may not be aware of all users that need to be in the directory/group.

To help us streamline your onboarding process, please ask your Juvare Professional Services Representative and Client Success Manager (CSM) for assistance identifying and coordinating with other stakeholders in your organization to prepare for potential workflow changes.

Users

To help your users prepare for accessing and using Juvare solutions, it is extremely helpful to provide them with some basic information before the solutions go live. To help you with this, refer to the following resources to prepare your users or troubleshoot potential issues:

• Juvare Login Services (JLS) FAQs

• Troubleshooting Login Issues

A unique email address is strongly recommended for each user. It identifies the person taking actions in your solution and supports accountability in reporting.

If your organization has traditionally used shared accounts for specific groups of users, you may want to reconsider this approach due to possible complications, such as failed logins and account lock outs. For example, a user that is logged in to a workstation with their personal credentials may not be able to log in to a shared account through the Juvare portal. This scenario will be further complicated if your organization wants to adopt multifactor authentication in the future.

Yes, SSO will only apply to your organization-specific email domain. Any other email domain, including Gmail addresses, will use the usual password reset process to access their accounts.

Yes, we have a workflow that would allow users to reset their password and log into their Juvare account in the event of an IT network failure. This workflow requires users to add a secondary email or cell phone number that can be used to get the password reset information. Refer to Set Up a Secondary Contact for more information.

Juvare supports two authentication methods: OpenID Connect (OIDC) and SAML 2.0.

• Open ID Connect (OIDC) is recommended for easier set up and long-term management.

• SAML 2.0 is preferred by some larger organizations for enhanced security.

Contact your Client Success Manager (CSM) to receive information on pricing for SSO and the appropriate documents to start the SSO setup process.