SSO Error - lastName Attribute

Bug Reports
1

Hello hello!

I sent multiple emails to [email protected] but have not heard anything back so I’m posting here in the hopes of getting some assistance here

I have a user completely unable to use Cursor since we enabled SSO, and when checking the logs I can see there’s a failure on the lastName attribute. Here’s a screenshot:

unnamed
unnamed710×129 4.55 KB

What I have tried:

  • Went into our provisioning tool, Rippling, to ensure the correct last name attribute was being passed through and ran a sync to ensure attributes are up to date
  • Confirmed I have attribute mapping setup per Cursor docs to pass the lastName attribute through the SSO app I created in Google Admin
  • Manually update the user’s last name to take out the “ñ” character in case it was considered “special”

Thanks so much!

2

You should be glad that you haven’t successfully bound it yet. Stop now—Cursor’s SSO hasn’t completed P0 testing.

refs:

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.