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

Slack integration auth issue #71448

Open
rohitdhas opened this issue May 16, 2024 · 6 comments
Open

Slack integration auth issue #71448

rohitdhas opened this issue May 16, 2024 · 6 comments

Comments

@rohitdhas
Copy link

Self-Hosted Version

24.1.0

CPU Architecture

x86_64

Docker Version

26.1.1

Docker Compose Version

v2.27.0

Steps to Reproduce

Click Settings > Integrations > Slack > Add Workspace

I encountered an error stating that the redirect URI didn't match any configured URIs. Passed URI: http://<server_ip_addr>:9000/auth/slack.callback.

I have added the Redirect URL in Slack, which is now https://<server_ip_addr>:9000/auth/slack.callback. because Slack only supports HTTPS. However, I'm still facing the issue.

Expected Result

redirect uri should have https instead of http.
Found similar issue - chsasank/outline-wiki-docker-compose#34

Actual Result

Screenshot 2024-05-16 at 1 26 36 PM

Event ID

No response

@hubertdeng123
Copy link
Member

Hi there, could you explain how you configured https for your instance? This could be the reason you are experiencing this issue.

@rohitdhas
Copy link
Author

rohitdhas commented May 20, 2024

This is default nginx config:

server {
    listen 80;
    server_name <my_server_domain>;

    location / {
        proxy_pass http://127.0.0.1:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

server {
    listen               443 ssl;

    ssl                  on;
    ssl_certificate      /etc/ssl/certificate.crt;
    ssl_certificate_key  /etc/ssl/private.key;

    server_name  <my_server_domain>;
    access_log   /var/log/nginx/nginx.vhost.access.log;
    error_log    /var/log/nginx/nginx.vhost.error.log;

    location     / {
        proxy_pass http://127.0.0.1:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

@azaslavsky
Copy link
Contributor

I'm going to see what the integrations folks have to say about this - it may be a problem in sentry at large. At the very least, they know that codebase better, and may be able to provide hints as to where this is getting mangled.

@azaslavsky azaslavsky transferred this issue from getsentry/self-hosted May 23, 2024
@getsantry
Copy link
Contributor

getsantry bot commented May 23, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented May 23, 2024

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

@Dhrumil-Sentry
Copy link

Thanks for this report, we're adding this to our backlog and we'll comment here as we have any updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: No status
Development

No branches or pull requests

4 participants