Comprehensive data protection for all workloads
Post Reply
AlexComputerGuy
Novice
Posts: 7
Liked: never
Joined: Dec 21, 2020 12:15 am
Full Name: AlexComputerGuy
Contact:

Feature Request : Emails not working Authorize again in the daily report

Post by AlexComputerGuy »

Feature Request in the daily reports! (Veeam Backup and Replication, all versions).

For I don't know what reason, my email reports stopped working, and when I went to the Options - Email Settings tab, there was the blue text to "Authorize".

So I did, and now I have the "Token is valid".

So my suggestion is when emails are not working, it should be a warning line in the Job logs "Emails are not working : please Authorize again", or something more clear :)

Thanks.
Gostev
Chief Product Officer
Posts: 32362
Liked: 7719 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by Gostev »

@Egor Yakovlev it's a very important warning as I believe it's going to happen quite often with modern authentication? Like you need to renew token every 90 days or something? May be we should add warning in 12.3.1
Egor Yakovlev
Product Manager
Posts: 2602
Liked: 718 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by Egor Yakovlev »

Sounds like a wonderful idea.
We do get and use refresh token, but I will check with it's lifetime settings and provide a way to be aware of it's expiration.

/Thanks!
Egor Yakovlev
Product Manager
Posts: 2602
Liked: 718 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by Egor Yakovlev » 1 person likes this post

Update.
- when authorizing, we are retrieving an access token (default lifetime = 15mins, controlled from oAuth side) and a refresh token (lifetime = unlimited). Access token has it's lifetime presented to us, and once we see it expires, we use refresh token to gain a new access one. This happens at the background and totally transparent to the user.
- the only way our refresh token is not able to obtain a new access token when needed, is when oAuth service administrator explicitly revokes it.
- when(if) such case happens, we already have job session warnings "Sending email report: cannot find a valid security token please re-authorize the application..." however this warning is considered lowest severity and does not change status of entire job session to Warning.

Having that said, Alex, please check your green job sessions for warnings. If they are there, that means we might need to raise the severity for that line and turn entire backup job yellow for such cases. If you don't see the warning, but token requires re-authentication, we will be glad to investigate that job logs with support team!
AlexComputerGuy
Novice
Posts: 7
Liked: never
Joined: Dec 21, 2020 12:15 am
Full Name: AlexComputerGuy
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by AlexComputerGuy »

> If you don't see the warning, but token requires re-authentication, we will be glad to investigate that job logs with support team!

Yes, that's meee! I have put all the details in the case #03414122.

Thanks.
Egor Yakovlev
Product Manager
Posts: 2602
Liked: 718 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by Egor Yakovlev »

Log package contains some wrong files. Please use "Export logs for this job" option in the Support Information > Export Logs wizard.
Thanks!
AlexComputerGuy
Novice
Posts: 7
Liked: never
Joined: Dec 21, 2020 12:15 am
Full Name: AlexComputerGuy
Contact:

Re: Feature Request : Emails not working Authorize again in the daily report

Post by AlexComputerGuy »

Everything should be there now :)
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], d.artzen, emil.davis, MirkoKiel123 and 35 guests