Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] Google login not providing workspace details #79

Conversation

RishivikramN
Copy link
Collaborator

Description

When registering a user via google workspace details was not created for the user.

Cause:

  • The new change in user service creates a new user without workspace details initially from cognito trigger lambda. This impacts the existing user login code in mex, so changes are done accordingly.

How has this been tested?

E2E Testing

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Dependent PRs

  • [ ]

Checklist:

  • My code follows the code style of this project.

@RishivikramN RishivikramN requested a review from mukul-mehta June 7, 2022 07:02
@RishivikramN RishivikramN self-assigned this Jun 7, 2022
@linear
Copy link

linear bot commented Jun 7, 2022

WD-1327 [BUG] Google Login not providing workspace details

Describe the bug

  • When registering a user via google workspace details was not created for the user.

Cause:

  • The new change in user service creates a new user without workspace details initially from cognito trigger lambda. This impacts the existing user login code in mex, so changes are done accordingly.

Expected Behaviour

Google login should happen properly

Screenshots

If applicable

Additional Context

NA

@mukul-mehta mukul-mehta merged commit 061c63a into main Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants