Authentication methods

Prev Next

The Zilliant platform supports authentication through:

  • Magic links—Members enter their email address to receive a unique, one-time link to sign in.

  • Password authentication—Members enter their assigned username and a secret password to sign in.

  • Open Authorization (OAuth)—Members sign in by using a third-party application as identity providers.

Read this topic to learn more about these authentication methods.

Magic links

When signing in to Zilliant, members can choose to request a one-time link that enables authentication. Magic links offer several benefits: they’re convenient, simple to use, and secure.

How magic links work

  1. The member enters their email address at https://login.myzilliant.com , then selects Continue with email.

  2. The Zilliant server generates a unique, cryptographically secure token, then emails the member a link that contains the token.

  3. The member selects the Log in link in their email.

  4. The Zilliant server verifies the token and member.

  5. The member is signed in to Zilliant. The token is invalidated for re-use.

Enabling magic links

You don’t need to set up magic links. This authentication method is available to all members by default.


Password authentication

Members can choose to set and use a secret password to sign in to Zilliant. Passwords generally are less secure than magic links, so you should consider enabling multi-factor authentication (MFA) for this authentication method.

Enabling password authentication

You don’t need to set up password authentication. This authentication method is available to all members by default.

If you choose to enable MFA for password authentication, you have two options:


OAuth

The Open Authorization (OAuth) protocol enables Zilliant to authenticate members without requiring a username and password. Google and Microsoft are the supported OAuth providers for member authentication with Zilliant.

How OAuth works

  1. The member goes to https://login.myzilliant.com .

  2. If enabled, the member selects Google or Microsoft to sign in.

  3. Zilliant redirects the member to Google or Microsoft to sign in and approve the access request.

  4. The Google or Microsoft server issues an access token to delegate member access to Zilliant.

  5. The member is signed in to Zilliant.

Enabling OAuth

You don’t need to set up OAuth. This authentication method is available to all members by default.

When a member signs in through Google or Microsoft, what is their session length?

For Google, sessions are limited to 60 minutes before a member has to re-authenticate. For Microsoft, the session is between 60 and 90 minutes long.