I’m an immich user, switching from a standard u/p login to an SSO-based login.
I’ve tested the SSO login successfully, it seems to work, and I’m not having any issues with that.
However, the account generated by SSO login has a different email address and identifiers from the account I created earlier. I don’t want to start from scratch with my photos, as I’ve spent countless hours updating metadata.
I think I need one of the following:
a supported, tested way to merge an account with another account. I don’t know if this is going to be similar to the “partner sharing” feature. I don’t want to simply share the photos, I want to have full control over them; including, if I delete a photo, it’s gone forever.
a tested way to manually update the database to change all identifiers over to the new account
a way to login to the existing account via my SSO portal. I can create any SSO user I want, for example.
a way to export the entire library with metadata and re-import it to the new SSO account, structured exactly the same way. Ideally this would also restore anything ML has done with my photos, but it’s not a disaster if I have to wait for ML to recreate what it already did in the new account.
Does anyone have information on how to achieve one of the above?
Followup question:
can anyone confirm with certainty that metadata changes I made in immich have been saved in the image files in /library/upload/*? I am already making backups (both pg_dump and the entire contents of the library), but it would be nice to know where the metadata is actually kept, in case I have to do DR.
I’m pretty sure it’s a lot easier than all of that. Account settings -> oauth -> link to oauth. That’s it. Maybe gets more complicated but sounds like that should be it for your use case.
This is the answer. Otherwise, you’ll need to go into the DB and perform a migration of the objects to that new user, but the chances you’ll cover all the bases there and not cause issues will be slim.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I’m pretty sure it’s a lot easier than all of that. Account settings -> oauth -> link to oauth. That’s it. Maybe gets more complicated but sounds like that should be it for your use case.
This is the answer. Otherwise, you’ll need to go into the DB and perform a migration of the objects to that new user, but the chances you’ll cover all the bases there and not cause issues will be slim.
Thanks! I’ll try this and report back. This sounds like a version of (#1) - merge accounts.