tchapi
5.0.2: add support for app keys?
Hi. Connecting your calendar backend to various scheduling tools, like let's say https://app.cal.com/apps/caldav-calendar creates an authentication problem.
If using LDAP authentication, ideally one wouldn't share their primary account password to various 3rd party services.
App keys, or "shared secret (hash?)" calendar links could possibly be a solution here, where we could supply 3rd party services an easily disposable or renewable secret.
Your thoughts?
Hi @lkraav 👋🏼
I'm not sure what you have in mind with app keys exactly. You want some kind of machine to machine interoperability (ie a machine impersonating a user to create an event on their behalf)?
You want some kind of machine to machine interoperability (ie a machine impersonating a user to create an event on their behalf)?
Yes, that's exactly how Calendly, cal.com etc works.
Scheduling is huge business, because it's mission critical.
«Create» may be step 2, but Read caps just to know freebusy / availability is maybe a starting point.