It sounds like you're experiencing some confusion with the authentication setup in your FusionAuth application. When using traditional email + password authentication alongside Google login, you're expecting to see distinct information in the user session to differentiate between the two authentication methods.

In the context of your Express.js application, the req.session.user object should ideally provide some form of identity provider identification to distinguish between users authenticated via traditional email + password versus Google login. However, it appears that you're not seeing this distinction reflected in the session information.

This behavior could be due to how FusionAuth handles user authentication and session management. It's possible that FusionAuth is not explicitly adding information about the identity provider to the user session, leading to ambiguity when accessing the session data in your Express.js application.

To address this issue, you may need to customize your FusionAuth setup or modify your Express.js application logic to explicitly capture and store information about the identity provider used during authentication. This could involve updating your authentication middleware or incorporating additional FusionAuth API calls to retrieve and store identity provider information alongside user session data.

In summary, while the lack of distinction between authentication methods in the user session may not be the expected behavior, it's likely a result of how FusionAuth is configured or how session information is managed in your application. By exploring customization options and making adjustments to your application logic, you should be able to achieve the desired differentiation between traditional email + password and Google login authentication methods.

To call a Google API or retrieve Google credentials, you typically need to follow these steps:

Create a Project in the Google Cloud Console:

Go to the Google Cloud Console.
Create a new project or select an existing one.
Enable APIs:

In the Cloud Console, navigate to the "APIs & Services" > "Dashboard."
Click on "+ ENABLE APIS AND SERVICES."
Search for the API you want to use (e.g., Google Drive API) and enable it.
Create Credentials:

After enabling the API, go to "APIs & Services" > "Credentials."
Click on "Create Credentials."
Choose the type of credentials you need (API key, OAuth client ID, etc.).
Configure OAuth Consent Screen:

If you're using OAuth, set up the OAuth consent screen with the required information.
Download or Copy Credentials:

Once you've created credentials, download or copy them. For OAuth client IDs, you might download a JSON file that contains your client ID and client secret.
Use Credentials in Your Code:

Integrate the credentials into your code. For example, if you're using OAuth, you'll use the client ID and secret to authenticate your application.

Make sure to replace 'credentials.json' with the path to your downloaded JSON file containing the client ID and secret.

Remember to handle your credentials securely and never expose them in publicly accessible code or repositories.

Distinguishing between Google Logins and traditional email + password logins involves the following:

User Input:

Traditional Login: Email + password manually entered.
Google Login: Authentication using Google credentials.
Authentication Protocol:

Traditional Login: HTTPS and direct password verification.
Google Login: OAuth or OpenID Connect for secure, third-party authentication.
User Experience:

Traditional Login: Password entry and recovery mechanisms.
Google Login: Streamlined process without password entry.
Security:

Traditional Login: Relies on password strength.
Google Login: Enhanced security with Google's features.
In summary, traditional logins use manual email + password entry, while Google Logins leverage Google credentials and advanced authentication protocols for a more streamlined and secure process.