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

[BUG]: Custom Google OAuth fails with insecure warning #4665

Open
Startouf opened this issue May 11, 2024 · 0 comments
Open

[BUG]: Custom Google OAuth fails with insecure warning #4665

Startouf opened this issue May 11, 2024 · 0 comments
Labels
🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces

Comments

@Startouf
Copy link

Startouf commented May 11, 2024

Describe the bug
When trying to set up a custom Oauth login for a google form connection, Google returns a security warning.

I tried setting up a custom OAuth app because when I use the regular Oauth screen, it does not find my Google forms stored on my shared Google Drive (and owned by the Shared google drive folder / the org)

To Reproduce
Steps to reproduce the behavior:

  1. Add a google form connection
  2. Click on 'I would like to use my own app credentials'
  3. Add a client ID and client secret from a configured OAuth credentials on GCP
  4. See error

Expected behavior
There should not be a connection error

Screenshots
Screenshot 2024-05-11 at 12 01 53

Additional context
Using the helm chart from there #4084 with docker image tagged 0.25.1

EDIT : It seems to be coming from the Redirect URL that is stuck at "https://activepieces.local:80/redirect". How can I tell activepieces I'm running under a different domain for OAuth login ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces
Projects
None yet
Development

No branches or pull requests

2 participants