Passport SDK v5.0
  • Overview
  • Account Lifecycle
  • Integration
    • Client Side Enablement
    • Credenza Presence (Optional Visual Elements)
    • Account Provisioning (Sign-up)
      • New Authentication System
      • Existing Authentication System - New Customer
      • Existing Authentication System - Existing Customer
  • Passport Subsequent Logins
  • Post-Login Capabilities
    • Account Information Access
    • Blockchain Wallet Access
  • Smart Contract Interactions
    • Instantiating The Contract Object (Server-Side)
    • Instantiating The Contract Object (Client-side)
    • Calling Contracts
  • Monetary Transactions
  • Appendix I: Passport Configuration Options
    • Magic
    • Ethers.js
    • Installation
    • Usage
    • Passport Instance Properties
    • Passport Static Properties
    • Modes
    • Supported query params
  • Transaction UI v3.0 (now part of Passport)
    • Magic
    • Ethers.js
    • Installation
    • Usage
    • Apple Pay
    • Google Pay
    • Methods
    • Events
  • Appendix II: MetaMembership Contract Access
  • Appendix III: Ledger Contract Access
  • Appendix IV: Decentralized Commerce Configuration
Powered by GitBook
LogoLogo

©2023 Credenza. All rights reserved.

On this page
  1. Integration

Account Provisioning (Sign-up)

Credenza Passport is built on top of the Magic Link system. This allows us to leverage their password-less authentication and secure storage of blockchain keys that allow clients and users to focus more on user experience and less on the complexities of blockchain development. In order to maintain secure access to the blockchain wallet, a specific workflow is required when a user authenticates to prevent unauthorized access to the blockchain wallet. This starts with the initial registration process.

To register an account, the end user must confirm ownership of an email address through our system. Even if the email address has already been verified in another manner, we need our system to confirm the address. However, there are multiple ways to launch this verification process depending on the system that is being integrated. There are three common scenarios:

  • A net new authentication system that will rely on Passport as their primary single-sign on (SSO) source. In this situation, no accounts need to be migrated and Credenza’s login system can provide the end-to-end experience.

  • An existing authentication system with existing login user experiences that wishes to migrate existing customers over. As mentioned earlier, Credenza Passport still requires the user to confirm with our system.

  • An existing authentication system with existing login user experiences that wishes to become part of the existing registration process to new customers. As mentioned earlier, Credenza Passport still requires the user to confirm with our system.

The following section will address each of these scenarios.

PreviousCredenza Presence (Optional Visual Elements)NextNew Authentication System

Last updated 2 years ago