K1000 O365 OAuth credential not working
Today we upgraded to v10.2.234, enabled SSL, and created the Office365 credential to use OAuth authentication for our service desk mailboxes. Unfortunately, messages are continuing to build up in our mailbox instead of being pulled into Kace. I have a ticket open with Quest support. Has anybody tried using this new authentication in Kace yet?
3 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
KevinG
4 years ago
Hi Jon,
Can you check that email is now working.
Comments:
-
I don't know what changed since working with support until after 5 yesterday, but it's working! - JonHall 4 years ago
-
I applied a fix to your appliance. Thanks for the confirmation that it is now working. - KevinG 4 years ago
-
do you recall the hot fix that was applied? - SandMan005 4 years ago
-
KevinG, we are having the same issue here, what fix did you apply . we are on 11.0.273 + hotfix 11 email update - 2Leo 3 years ago
-
@SandMan005 - Unfortunately, I never found out. Maybe @KevinG can assist? - JonHall 4 years ago
-
I'd like to know too. We have two issues with Oauth. 1. In Azure, must set app reg to multitenant. We think this is an unnecessary security risk. 2. Mail is not deleted, its just marked read. - barchetta 4 years ago
Posted by:
2Leo
3 years ago
Posted by:
KevinG
4 years ago
Can you please click the enable tether button in 10.2 that will automatically apply a key to your appliance.
This will allow KACE to further investigate. - KevinG 4 years ago
I attempted to send the tether key via an email reply Friday, but none of those messages were added to the request for some reason. Due to the length of the tether key I broke it into two notes added to the request. - JonHall 4 years ago
Do you remember if you have SMTP enabled in Network Settings and inside each queue?
Or migrating to Oauth authentication, means we can get rid of smtp settings? - Channeler 4 years ago