Nuxt Authentication

[exonomyapp]

Children:

The following is a list of authentication providers currently supported by Exosystems.net

• [ ] Google
• [ ] GitHub
• [ ] MetaMask
  • [ ] DIDs

[exonomyapp]

Detailed issues in the description

[exonomyapp]

Here's what we can use to redirect users right after they try to log in: https://nuxt.com/docs/api/utils/define-nuxt-route-middleware#redirection

[CompileWithG]

Work Track Update First Work Track: Our primary focus has been on providing ongoing support for the solution that our team has already implemented, which involves storing data directly into SQLite3. Although we’re not calling this setup “production,” it is already in use. We're now moving forward by involving other team members to build the UI experience for our newly authenticated users. This includes developing a dashboard and incorporating their GitHub highlights.

To tackle this broader task, we’ll be assembling a team. These team members will require support from time to time, and we'll continue using the same branch for any necessary modifications to our data model as we progress. Team members are expected to accept and address issues created by others, which may be assigned or delegated to them.

Second Work Track: With the direct connection to the SQLite3 database established, our next step is to implement Drizzle in the Nuxt authentication layer. This ORM layer will streamline the transition from authentication to other features that require data persistence. We will create a different branch dedicated to the Drizzle implementation. Before diving into the implementation, we need to allocate time for learning about Drizzle, reviewing example code structures, and gaining a solid understanding of how it works.

This comment summarizes the current progress and future steps for both work tracks, helping the team keep track of our work history.

[exonomyapp]

Work Track Update First Work Track: Our primary focus has been on providing ongoing support for the solution that our team has already implemented, which involves storing data directly into SQLite3. Although we’re not calling this setup “production,” it is already in use. We're now moving forward by involving other team members to build the UI experience for our newly authenticated users. This includes developing a dashboard and incorporating their GitHub highlights.

To tackle this broader task, we’ll be assembling a team. These team members will require support from time to time, and we'll continue using the same branch for any necessary modifications to our data model as we progress. Team members are expected to accept and address issues created by others, which may be assigned or delegated to them.

Second Work Track: With the direct connection to the SQLite3 database established, our next step is to implement Drizzle in the Nuxt authentication layer. This ORM layer will streamline the transition from authentication to other features that require data persistence. We will create a different branch dedicated to the Drizzle implementation. Before diving into the implementation, we need to allocate time for learning about Drizzle, reviewing example code structures, and gaining a solid understanding of how it works.

This comment summarizes the current progress and future steps for both work tracks, helping the team keep track of our work history.

I prepared a little gist about fully typing our code for direct access to SQLite3: https://gist.github.com/exonomyapp/fb875a51da269b37e8cbfbe1f1b1c2eb

[exonomyapp]

adding comment to test parent child update

[exonomyapp]

adding comment to test parent child update

[exonomyapp]

One thing we can add to the Authentication flow in cases when it succeeds but for a new user is to assign that new user our own UUID. This UUID can then be used to create new IPFS documents and Wallet accounts for most crypto wallets.

crypto.randomUUID() is a method in modern web APIs that generates a universally unique identifier (UUID) in a secure and random manner. It adheres to the UUID version 4 format, which is typically used for generating random-based UUIDs.

Example usage:

javascript const uuid = crypto.randomUUID(); console.log(uuid);

Output:

It will generate a string like:

4b1b68d9-3e8e-4b14-908f-2b60eb1e7659

Key Points:

• Secure: It uses a cryptographic random number generator, making it suitable for scenarios requiring a high degree of randomness and uniqueness.
• Modern: Supported by modern browsers and environments (like Node.js).
• No dependencies: Unlike many older UUID generation libraries, you don’t need any additional packages or dependencies.

It’s especially useful in web or serverless environments where you need to generate unique identifiers securely, for example, when creating unique user IDs, session tokens, etc.