Has anyone ever had a new workspace created automatically and the original workspace removed from that authentication when using a Google account to authenticate? When using the direct workspace url to try and access, I get 403 error.

I'm sorry, but the knowledge sources do not contain any information about issues where a new workspace is created automatically and the original workspace is removed from authentication specifically when using a Google account to authenticate. There is also no mention of this scenario causing a 403 error when accessing the direct workspace URL. However, there are some general notes about 403 errors: - A 403 Forbidden error can occur if the token scope does not match the target workspace or if there are insufficient permissions for the operation. For example, a scoped token only allows access to its specific workspace, and using it for another workspace will result in a 403 error. Solutions include verifying that the token scope matches the workspace and using the correct token type for the operation [Error responses](https://docs.airbyte.com/ai-agents/embedded/api/authentication#error-responses). - There is also a forum post where a user encountered a 403 error due to a mismatch between the workspace UUIDs after restarting Airbyte and the webapp, but this was not related to Google authentication [Failed to create postgresql source](https://discuss.airbyte.io/t/1902). If you are experiencing this issue, it may be related to token scope or workspace permissions, but the knowledge sources do not provide a direct answer regarding Google authentication or automatic workspace creation/removal.

Are you talking about on Airbyte Cloud SSO, or using a Google Account to access a self-deployed OSS cluster (i.e. using Cloud Identity-Aware Proxy)?

@Justin Beasley I'm using Aribyte Cloud SSO, using a Google account for login. Each time the session logs me out and I use Google as SSO, a new workspace is created in Airbyte Cloud.

Hm, seems like a bug you'll need to run through their support. For now you may be able to work around it by using normal password auth though