Corporate policy and Oauth2 tokens
-
Absolutely loving the ability to have a calendar in my browser, and I'm hoping to be able to use it with my work account too. Because we're a security minded company, we've got our gmail/calendar settings pretty locked down, and so when attempting to add my work calendar to Vivaldi I get a 400 authorization error.
I've spoken to our security admin, and he's open to the idea of adding Vivaldi to our "blessed" applications, but he's curious as to why Oauth2 tokens are necessary at all to interface with google's calendar/email, and also curious where those tokens are stored (are they within the Vivaldi app itself? on Vivaldi's servers? etc)
Does anyone have any details that may shed light on this? Would be grateful for any help!
-
Hi @nullset.
I hope you will like and use Vivaldi Calendar.
In order for Vivaldi to connect to Google CalDAV API, OAuth 2.0 must be used as authentication method.
Vivaldi stores the OAuth token within the app. Never on any servers.Regards Gudmundur Arnar
-
@arnar Thank you so much for the quick reply! I'll forward the information on to our internal security team. I'm really loving Vivaldi's calendar for my personal use. Massive thanks to the Vivaldi team for building a better browser
-