We’re exploring embedding some LiveWhale calendar widgets on intranet pages behind SSO to share upcoming events. Does anyone know if there are any limitations or display issues related to the login requirement?
Hi Karie,
Sure thing, this comes up from time to time.
Showing “Any logged-in user” events in LiveWhale requires an active login session made through the LiveWhale/SSO connection (usually a SAML connection). That’s why on main calendars, we often suggest adding a login link if people plan on using the “Any logged-in user” privacy setting.
I don’t think there’s currently a way we can have a LiveWhale SSO connection be “seen” via a widget injected onto another page, so that may be a limitation depending on how you’re imagining using this. (Others, feel free to pipe up if you’ve got this working in a way I’m not aware of 
).
Otherwise, we definitely do have plenty of folks who use LWC Widgets on their intranet sites, but usually those are displaying already Public (privacy = Everybody) events. Sometimes for “soft permissions” there may be a special tag, group, or event type that gets excluded from the main calendar views, and then that does get pulled into the intranet widget, but that’s not quite the same thing as requiring a login.
(For more bespoke API integrations, it is possible to use ?lw_auth= authentication tokens to make authenticated requested and get private results.)
Hope this helps, let me know if it’d be useful to chat more about this, either in terms of what’s possible out-of-the-box or perhaps with some minor customizations. Thanks!