old api key on a new server

[Alexwerilles 3]

I changed the hosting emby server, backed up the settings and restored it to the new server. Turns out the api key wasn't restored on the new server either. Is there a possibility that I can use the old api key on the new server? How can I do it? I need the old key to be able to administer users

[Luke 37060]

Hi, yes this is something we can look at adding to the backup and restore plugin. Thanks.

[Alexwerilles 3]

On 8/29/2021 at 11:29 AM, Luke said:

Hi, yes this is something we can look at adding to the backup and restore plugin. Thanks.

How can I add the old API key manually on the new server?

or use the old server's database on the new server

[Luke 37060]

53 minutes ago, Alexwerilles said:

How can I add the old API key manually on the new server?

or use the old server's database on the new server

Hi, have you explored the API keys menu in the server?

[Alexwerilles 3]

1 minute ago, Luke said:

Oi, você explorou o menu de chaves de API no servidor?

not. Where do I find this menu?

[Alexwerilles 3]

If it is the option "Api keys" which is on the left menu, there is only the option to create a new key

[Luke 37060]

Right OK, sorry. There currently is no way to add the old one.

[Alexwerilles 3]

there is not even the option to add manually?

[Luke 37060]

7 minutes ago, Alexwerilles said:

there is not even the option to add manually?

I agree it's something we need to add, and we can look at it, but there is currently no function to do that.

[Happy2Play 8281]

1 hour ago, Luke said:

Right OK, sorry. There currently is no way to add the old one.

Can the key be manually added into the authentication.db?

1 hour ago, Alexwerilles said:

there is not even the option to add manually?

Do you still have the old authentication.db?

[Alexwerilles 3]

2 hours ago, Happy2Play said:

Can the key be manually added into the authentication.db?

Do you still have the old authentication.db?

I think I have

[Alexwerilles 3]

yes I have access

[Happy2Play 8281]

21 minutes ago, Alexwerilles said:

I think I have

 

14 minutes ago, Alexwerilles said:

yes I have access

You should be able to restore that database.  I have tested backing up my current authentication.db, shutting down Emby deleting the authentication.db and starting Emby to see no current api keys, then shutdown Emby and restored the authentication.db and started Emby to have the keys restored.

Or you could manually copy the keys from one database to the other.

Edited August 30, 2021 by Happy2Play

[Alexwerilles 3]

3 minutes ago, Happy2Play said:

 

You should be able to restore that database.  I have tested backing up my current authentication.db, shutting down Emby deleting the authentication.db and starting Emby to see on current api keys, then shutdown Emby and restored the authentication.db and started Emby to have the keys restored.

Or you could manually copy the keys from one database to the other.

Okay, recap:

I shut down the emby server, delete the "authentication.db" from the current server.
copy the "authentication.db" from the old server, put it on the new server and start the emby server?

[Alexwerilles 3]

can i do this also with the user.db file? So that I can use the same users from the old server? As if nothing has changed, etc?

[Happy2Play 8281]

Just now, Alexwerilles said:

Okay, recap:

I shut down the emby server, delete the "authentication.db" from the current server.
copy the "authentication.db" from the old server, put it on the new server and start the emby server?

Yes, but I would back up current one before replacing.

Just now, Alexwerilles said:

can i do this also with the user.db file? So that I can use the same users from the old server? As if nothing has changed, etc?

Yes you can, but I thought you used the Server Configuration Backup Plugin which already does this for users and userdata assuming you restored that info.

[Alexwerilles 3]

Just now, Happy2Play said:

Yes, but I would back up current one before replacing.

Yes you can, but I thought you used the Server Configuration Backup Plugin which already does this for users and userdata assuming you restored that info.

Yes, I have already backed up the files.

It's because I restored the backup a few days ago, since then users have already made some changes to their accounts, so I wouldn't have to restore the backup again, I would just replace the user.db file...

I will do a test.

In addition to this file, there are also files:

 

"authentication.db-shm" and "authentication.db-wal"
"users.db-shm" and "users.db-wal"

 

also replaces or does not need?

[Happy2Play 8281]

1 minute ago, Alexwerilles said:

In addition to this file, there are also files:

 

"authentication.db-shm" and "authentication.db-wal"
"users.db-shm" and "users.db-wal"

 

also replaces or does not need?

Those files only exist on OPEN databases, so no you would never restore those files.

[Alexwerilles 3]

8 minutes ago, Happy2Play said:

Yes, but I would back up current one before replacing.

Yes you can, but I thought you used the Server Configuration Backup Plugin which already does this for users and userdata assuming you restored that info.

Perfect worked. However, the old API only works when I also replace the "users.db" file with the "users.db" file also from the old server.

However, all users are activated and with administrator status, when I put the "user.db" from the old server.

[Happy2Play 8281]

11 minutes ago, Alexwerilles said:

Perfect worked. However, the old API only works when I also replace the "users.db" file with the "users.db" file also from the old server.

However, all users are activated and with administrator status, when I put the "user.db" from the old server.

Some databases and tables in old databases are obsolete.

But am guessing the old users.db does not match the "*\programdata\config\users" and new folders  with new config and policy xmls are/were created.

Just like moving a users.db can mis-align userid userdata in the library.db if they are not moved together.  But the library.db has a dependancy on /metadata/library also.

This is why moving databases alone will be problematic in most cases.  It is somewhat a package deal when it comes to the programdata folder.

Ideally you would use the plugin for users and userdata to maintain this alignment

[Alexwerilles 3]

19 minutes ago, Happy2Play said:

Some databases and tables in old databases are obsolete.

But am guessing the old users.db does not match the "*\programdata\config\users" and new folders  with new config and policy xmls are/were created.

Just like moving a users.db can mis-align userid userdata in the library.db if they are not moved together.  But the library.db has a dependancy on /metadata/library also.

This is why moving databases alone will be problematic in most cases.  It is somewhat a package deal when it comes to the programdata folder.

Ideally you would use the plugin for users and userdata to maintain this alignment

Understand.

No problem. I will edit the status of users one by one. Thanks a lot for the help!