Repository navigation
OIDC multi user login vs service API keys #25
Replies: 1 comment 1 reply
|
Hi @tedstriker thanks for the kind words, glad you're liking it! What you suggested makes a lot of sense. You read it right: sign-in is per person, but integrations use the keys in the config. Profiles decide which cards someone sees, not whose data is behind them. New in 0.8.0: each person's own activity on shared services. Many services already know whose activity is whose with one admin key, so you can tell Valet each person's username there: integrations:
plex:
type: tautulli
url: http://tautulli:8181
apiKey: ${TAUTULLI_KEY}
people: { sam: samantha, alex: alex.k } # Valet sign-in name → their name on this serviceThen Sam sees her own now playing, history and stats and Alex would see his. It works for Tautulli (Plex), Jellyfin, Emby (continue watching, recently added), Seerr (their requests, and requests the assistant makes for them are filed under them) and Audiobookshelf. Anyone not listed sees what they see today; owners can switch to everyone's from ⌘K. Docs: https://askvalet.dev/start/people/#their-own-plex-jellyfin-and-requests Possible today for everything else: for services where each person has their own API key (Immich, Paperless, Karakeep and similar), give each person their own instance with their key, on a tab only their profile sees: integrations:
photos_sam: { type: immich, url: http://immich:2283, apiKey: "${SAM_IMMICH_KEY}" }
layout:
- title: Sam
widgets: [photos_sam.memories]
profiles:
sam: { tabs: [Sam, Media] }
users: { sam: sam }It works, but not ideal since you collect everyone's keys and the config grows with each person. Would these help you?
Which services would you want this for, and would (1) cover your setup? That will help me decide what comes next. Thanks |
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
I came across Valet through the selfh.st newsletter, and I think you did an impressive job @IbrahimIrfan!
While going through the docs, I noticed that OIDC can be used to sign in (very good!), but the integrations use static API keys in the YAML config, if I got that right.
The consequence is that every user would see my progress videos, my latest photos from Immich, my ...
Wouldn't it make more sense for everyone to see their own content from the services they want to use?
In my mind this is just one abstraction layer away: services are discovered via YAML or the Docker socket, and users would then select which services they use — and, more importantly, with which account.
A bonus would be reusing the OIDC SSO so a single login suffices.
That's just my take on this.
Anyways — keep up the good work!
All reactions