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

Ombi with Oauth enabled and MobileApp Access #221

Open
IrishTR opened this issue Jan 20, 2022 · 3 comments
Open

Ombi with Oauth enabled and MobileApp Access #221

IrishTR opened this issue Jan 20, 2022 · 3 comments

Comments

@IrishTR
Copy link

IrishTR commented Jan 20, 2022

Hi, first off your work has enabled me to accomplish a great many things with my setup, thank you very much.

On to my question I saw previous issue where folks needed to bypass Authelia/Google OAuth for API access for things like Tautulli, Radarr, Sonarr, etc. I've got all that working great. My last hold out is the Ombi piece. Not sure what needs to happen to have OAuth enable and allow API and or the Mobile App to still function (similar to Tautulli). I tried the API bypass options used for those other apps listed but don't seem to be making headway and not sure where to begin tracking down if its something I need to tweak or just not feasible.

Thank you.

@IrishTR IrishTR changed the title Ombi with Oauth enabled and App Access Ombi with Oauth enabled and MobileApp Access Jan 20, 2022
@IrishTR
Copy link
Author

IrishTR commented Jan 20, 2022

ombi:
image: linuxserver/ombi:latest
container_name: ombi
restart: unless-stopped
networks:
- t2_proxy
security_opt:
- no-new-privileges:true
volumes:
- $DOCKERDIR/ombi:/config
environment:
PUID: $PUID
PGID: $PGID
TZ: $TZ
BASE_URL: /ombi #optional
labels:
- "traefik.enable=true"
- "traefik.http.routers.ombi-rtr.entrypoints=https"
- "traefik.http.routers.ombi-rtr.priority=99"
- "traefik.http.routers.ombi-rtr.rule=Host(ombi.$DOMAINNAME)"
- "traefik.http.routers.ombi-rtr.middlewares=chain-oauth@file"
- "traefik.http.routers.ombi-rtr.service=ombi-svc"
- "traefik.http.services.ombi-svc.loadbalancer.server.port=3579"
## API Oauth Bypass
- "traefik.http.routers.ombi-rtr-bypass.entrypoints=https"
- "traefik.http.routers.ombi-rtr-bypass.rule=Headers(X-Api-Key, $OMBI_API) || Query(apikey, $OMBI_API)"
- "traefik.http.routers.ombi-rtr-bypass.priority=100"
- "traefik.http.routers.ombi-rtr-bypass.middlewares=chain-no-auth@file"
- "traefik.http.routers.ombi-rtr-bypass.service=ombi-svc"

@robflate
Copy link
Contributor

Haven't checked on this in a while but Traefik used to throw errors and quietly fail when adding those headers to Ombi.

Not as secure but you could bypass;

- "traefik.http.routers.ombi-rtr-bypass.rule=Host(`ombi.$DOMAINNAME`) && PathPrefix(`/api/`)"

@uasdj25
Copy link
Contributor

uasdj25 commented Jan 26, 2022

Yep, I was told on Ombi discord a while back that it wasn't feasible with Google Oauth. There is, however, the ability to use Plex Oauth that is embedded within the app. I haven't gone back, so this might not be the case anymore (the inability to leverage oauth from Google through Traefik), but to my knowledge not doable. I have it just using oauth from Plex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants