-
-
Notifications
You must be signed in to change notification settings - Fork 71
Instructions on how to install this with docker? #27
Comments
No luck so far. All I get is "No authentication providers are available.". The python install of Sentry is deprecated, but the Docker install doesn't seem to support this plugin. Also the official list of plugins doesn't list this one, nor does this plugin come preinstalled like others. A little instruction would go a long way. |
Update: See this #27 (comment) for version 9.1.1 Ok I figured it out (hopefully this helps someone who is looking for docker install instructions): if 'GOOGLE_CLIENT_ID' in os.environ:
GOOGLE_CLIENT_ID = env('GOOGLE_CLIENT_ID')
GOOGLE_CLIENT_SECRET = env('GOOGLE_CLIENT_SECRET') 4. Run the following 3 commands: |
can we maybe update readme? |
yes, please update the readme. This worked for me too! Thank you, @DevJackSmith! |
in the newest version (9.1.1) the above solution will give you a warning. Instead, I added the following to sentry.conf.py
|
For me on 9.1.0 only worked when i set on config.py:
|
9.1.x using the sentry-onbuild docker image - # Google Single Sign On
SENTRY_OPTIONS['auth-google.client-id'] = env('GOOGLE_CLIENT_ID')
SENTRY_OPTIONS['auth-google.client-secret'] = env('GOOGLE_CLIENT_SECRET') It's DevJackSmith's solution, but passed in with environment variables. |
Oddly, if I install both After giving up trying to deduce the conflict, I started doing some trial and error. Oddly, the original instructions in the readme are the only ones that worked, meaning set I am not sure why installing # Google Single Sign On
GOOGLE_OAUTH2_CLIENT_ID = env('GOOGLE_CLIENT_ID')
GOOGLE_OAUTH2_CLIENT_SECRET = env('GOOGLE_CLIENT_SECRET')
GOOGLE_CLIENT_ID = GOOGLE_OAUTH2_CLIENT_ID
GOOGLE_CLIENT_SECRET = GOOGLE_OAUTH2_CLIENT_SECRET
SENTRY_OPTIONS['auth-google.client-id'] = GOOGLE_OAUTH2_CLIENT_ID
SENTRY_OPTIONS['auth-google.client-secret'] = GOOGLE_OAUTH2_CLIENT_SECRET |
i think sentry plugins now includes google auth. So no need to install them separately. (You probably don't need 2 middle lines. The two top lines are just passing it from the environment variables into local variables and then again into local SENTRY_OPTIONS variables, so you might simplify it with just the two lines like this https://github.com/getsentry/sentry-auth-google#issuecomment-490260014 and it should still function just fine. If readme instructions work, i'm all for closing this issue. Can someone else confirm the readme instructions work for them now? |
Does the plugin package include google auth? I didn't see it here https://github.com/getsentry/sentry-plugins/tree/master/src/sentry_plugins If it's in there though, I have no problem uninstalling this package. Last I heard though, they hadn't merged the auth plugins with the rest of the plugins. I don't recall which thread I saw it in, but it sounded like the team hadn't gotten around to merging them yet. Though what you're saying is the only answer that makes sense why installing sentry-plugins changes the behavior of sentry-auth-google. |
You are right, i don't know if google-auth is included in sentry-plugins now, i just assumed it was since I had to remove the zip url from requirements.txt file, and I created the server from scratch without it. So it must be in there somewhere unless I missed something. |
FYI I happened to see this plugin is now included in sentry core now @DevJackSmith @caseyduquettesc getsentry/sentry#11769 |
I gave up... This masterpiece does not work at all. Took gitlab SSO instead https://github.com/SkyLothar/sentry-auth-gitlab which had zero update since two years and it worked out-of-the box instantly. |
Hi I followed the instructions on how to setup sentry from here:
https://github.com/getsentry/onpremise
And figured out that for email to work i need to add environment variables to the docker-compose.yml file. But just adding GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET to the same place does not work.
Do I need to download something somewhere? Or run the pip command inside a container? or how do I install it?
The text was updated successfully, but these errors were encountered: