Mail Fetching with oAuth2 only works once

KevinTheJedi

nda00

You need to show the settings of the scheduled task. Just the General, Triggers, and Actions tabs.

Cheers.

nda00

KevinTheJedi

Oh yeah, here you go:

KevinTheJedi

nda00

Okay, first the Triggers is a little off. You need to run indefinitely so it runs until you stop it. You also need to remove the "-f" from the command. Lastly, make sure the Actions has the command as the path to PHP, then put the path to the cron file in the Arguments box, then retest.

I know sometimes quotes messes things up as well so try removing those if the above doesn’t work.

Cheers.

nda00

KevinTheJedi

Thanks for the suggestions. I tested them but no luck unfortunately.

If I manually execute the command from cmd, it should technically work as well, right?
I've done this to see if it is something with the scheduled task itself. However it just keeps throwing the same PHP error that I sent in my first message.
Do you have any other ideas?

KevinTheJedi

nda00

Okay, go to to email table, find the email's ID, go to the email_account table, delete both records where email_id = the email ID from earlier, then go to the config table and delete the instance config and token information related to the email, then reconfigure the email.

Cheers.

nda00

KevinTheJedi

I'll need some help with the last step, as I can't seem to find a record in the config table which would relate to the email or mention "instance config" or "token".
How do I identify these?
Thank you

KevinTheJedi

nda00

If you go to the plugin_instance table you’ll see a record for the email address. Grab that record’s ID as well as the plugin_id value. Then search the config where namespace is plugin.plugin_id.instance.ID (replacing plugin_id and ID with the actual values. Then delete those and only those records. Then do the same but where namespace is email.email_id.account.email_account_id.

Cheers.

nda00

KevinTheJedi

My config table is devoid of any records containing "plugin" or "email" in the namespace. I assume that's what's causing the issue in the first place.

What I don't get is where the OAuth2 settings from the E-Mail configuration are saved if they aren't in the config table:

Is it possible to "repair" the config table? As in, write the missing records to the table?

KevinTheJedi

nda00

The _config table houses both the OAuth2 config and the Token information. OAuth2 config is stored in _config table under namespace -> plugin.plugin_id.instance.instance_id. Token information is stored in _config table under namespace -> email.email_id.account.account_id.

No, you cannot "repair" those records. They need to be generated from within the UI as some of the values are encrypted/hashed.

Cheers.

nda00

KevinTheJedi

So considering my situation, where via osTicket E-Mail Config all entries are there (see below) but they aren't saved in the config table, where could they be?

I've deleted the E-Mail addresses and OAuth2 instances via osTicket and then re-added them, but nothing gets written to the config table. Do you have any idea why this might be?

Thank you

KevinTheJedi

nda00

The filter option you are using is not working right. Simply look at all the values in the table. You will find them.

Cheers.

nda00

KevinTheJedi

The filter works in the config table on my test DB and returns the correct values. Anyways, I checked the config table on the live DB manually, the records are not there. I can send you an export of the table if you want

KevinTheJedi

nda00

Well idk what to tell you. They should be there. Maybe you’re looking at wrong db? Maybe you need to refresh you db client?

Cheers.

nda00

KevinTheJedi

I've done another reinstall, now the records are there. Idk what it was, maybe I missed them, maybe they weren't there, anyways, sorry for that.

I've now been able to fix the issue thanks to this where you suggested to delete any records from the email_account table, that don't have a matching record in the email table. After that, fetching worked again.

Thank you for your time and help in this case.