Documentation

Table of Contents


Other Resources


Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Expand
    titleUsername | Second Factor

    User provides username on one page, and then undergoes two-factor authentication on a subsequent page.

    This options requires configuration and enablement of at least one registration method on the Multi-Factor Methods tab.

  • Expand
    titleUsername | Second Factor

    User provides username on one page, and then undergoes two-factor authentication on a subsequent page.

    This options requires configuration and enablement of at least one registration method on the Multi-Factor Methods tab.

    Expand
    title(Valid Persistent Token) only

    User presents a valid persistent token in lieu of a username only (no password of second factor required).

    This option requires a different realm in which the Client Side Control token/certificate/fingerprint is generated for use on this realm.

  • Expand
    titleUsername & Password

    User provides username and password on one page (no second factor).

  • Expand
    titleUsername & Password | Second Factor

    User provides username and password on the page, and then undergoes two-factor authentication on a subsequent page.

    This options requires configuration and enablement of at least one registration method on the Multi-Factor Methods tab.

  • Expand
    titleUsername | Password

    User provides username on one page, and then provides password on a subsequent page (no second factor).

  • Expand
    titleUsername | Second Factor | Password

    User provides username on one page, undergoes two-factor authentication on next page, and then provides password on a subsequent page (standard workflow, recommended by SecureAuth).

    This options requires configuration and enablement of at least one registration method on the Multi-Factor Methods tab.

  • Expand
    title(Valid Persistent Token) | Password

    User presents a valid persistent token in lieu of a username on one page, and then provides password on a subsequent page (no second factor).

    This option requires a different realm in which the Client Side Control token/certificate/fingerprint is generated for use on this realm.

  • Expand
    title(Valid Persistent Token) | Second Factor

    User presents a valid persistent token in lieu of a username on one page, and then undergoes two-factor authentication on a subsequent page.

    This option requires a different realm in which the Client Side Control token/certificate/fingerprint is generated for use on this realm, and configuration and enablement of at least one registration method is made on the Multi-Factor Methods tab.

  • Expand
    title(Valid Persistent Token) | Second Factor | Password

    User presents a valid persistent token in lieu of a username on one page, undergoes two-factor authentication on next page, and then provides password on a subsequent page.

    This option requires a different realm in which the Client Side Control token/certificate/fingerprint is generated for use on this realm, and configuration and enablement of at least one registration method is made on the Multi-Factor Methods tab.

...

...

Certificate Based

...

 

...

Related topic

...