Passport SDK v8
  • 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
    • Credenza Core Web SDK (Auth)
    • Ethers.js
    • Installation
    • Usage
    • Passport Instance Properties
    • Passport Static Properties
    • Modes
  • Appendix IA: Transaction UI v3.0 (now part of Passport)
    • Installation
    • Usage
    • Apple Pay
    • Google Pay
    • Methods
    • Events
  • Appendix II: MetaMembership Contract Access
  • Appendix III: Ledger Contract Access
  • Appendix IV: Decentralized Commerce Configuration
  • Appendix V: Migration From Previous Passports
Powered by GitBook
LogoLogo

©2023 Credenza. All rights reserved.

On this page
  1. Integration

Account Provisioning (Sign-up)

Credenza Passport is constructed atop our proprietary Core Web SDK, which natively supports OAuth, Password, and Passwordless authentication options. While the blockchain keys remain custodial, the SDK is designed for seamless integration across a client's entire ecosystem of service providers, vendors, and sponsors. We manage the authentication process and provide convenient access to our secure storage of blockchain keys, allowing clients and users to focus more on user experience and less on the intricacies of blockchain development.

To ensure secure access to the blockchain wallet, a specific workflow is necessary when a user authenticates, preventing unauthorized access to the blockchain wallet. This workflow commences with the initial registration process.

During registration, users must verify ownership of an email address through our system. It's crucial to note that each email address necessitates the use of a singular modality for all subsequent logins. Therefore, if a user registers with johndoe@example.com using password-less authentication, that user cannot subsequently employ Google login or create a password for that account.

Launching the verification process can be executed in multiple ways, contingent upon the system being integrated. There are three common scenarios:

  1. A brand-new authentication system opting to rely on Passport as their primary single sign-on (SSO) source. In this scenario, no account migration is required, and Credenza's login system can furnish the end-to-end experience.

  2. An existing authentication system with pre-existing login user experiences intending to migrate existing customers. Despite this, Credenza Passport still necessitates user confirmation within our system.

  3. An existing authentication system with pre-existing login user experiences aiming to incorporate into the current registration process for new customers. Similar to the previous scenario, Credenza Passport still mandates user confirmation within our system.

The subsequent section will delineate each of these scenarios.

PreviousCredenza Presence (Optional Visual Elements)NextNew Authentication System

Last updated 1 year ago