mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#GraphAPI

0 Beiträge0 Beteiligte0 Beiträge heute
Antwortete im Thread

🧵 4/5 Until now, I have been using IMAP+SMTP, and TbSync for address books and calendars. After going through a few iterations, I have now settled on using Exchange (native, experimental) accounts (yes, plural) for email and sticking with TbSync for calendars and address books.

#thunderbird#tb140#TbSync
Antwortete im Thread

🧵 2/5 Further, the “native” connection to EWS/OWA within Thunderbird is only available in 140 when you enable a custom setting (search for “ews”). What you see in the new Account Hub will depend on whether that custom setting is enabled.

#thunderbird#tb140#TbSync
Antwortete im Thread

🧵 5/5 TbSync was a small challenge because, as has happened in the past with major Thunderbird updates, it was declared unsupported and automatically disabled by Thunderbird 140esr. Following the instructions in github.com/jobisoft/TbSync/iss (file-based reinstall of TbSync and EAS-4-TbSync) resolves the issue for now.

GitHubTB-Sync does not work with TB 140.0 ? · Issue #753 · jobisoft/TbSyncVon Thunderfan1980
#thunderbird#tb140#TbSync
Antwortete im Thread

🧵 3/5 Right now, Exchange requires add-ons to work. Usually this means TbSync or OWL. Each of these has its own set of features and limitations to consider. Account Hub will show you Exchange in two flavors… one says “add-on required” and the other doesn’t. It’s the latter one that is the native integration in experimental form at this time (and does email ONLY for now).

#thunderbird#tb140#TbSync

Today, we are thrilled to announce the release of the #MSExchange April 2025 Hotfix Update (HU)! This update is particularly significant for our hybrid customers as it introduces crucial changes in the integration between Exchange Server and Exchange Online.

This update lays the groundwork for transitioning to the Graph API as a replacement for EWS in Exchange hybrid environments.

For more details on this update and what’s coming next, be sure to check out our latest blog post. Stay informed and stay ahead!

#ExchangeServer #ExchangeOnline #GraphAPI #EWS

techcommunity.microsoft.com/bl

techcommunity.microsoft.com/bl

Aktuell vermehrt #Cyberangriffe auf #Owncloud-Instanzen - Patch für die ausgenutzte #Schwachstelle ist seit September 2023 verfügbar, allen Administratoren wird deshalb die dringende Aktualisierung der #Graphapi-App auf Version 0.3.1 nahe gelegt:
"Die bei den beobachteten Angriffen ausgenutzte Sicherheitslücke ist als CVE-2023-49103 registriert und mit dem maximal möglichen CVSS-Wert von 10 als kritisch eingestuft." #cybersecurity #cybersicherheit
golem.de/news/patch-verfuegbar

Golem.de · Patch verfügbar: Kritische Owncloud-Lücke wird vermehrt attackiert - Golem.deVon Marc Stöckel

Some Graph API fun today.

The Graph API knows `applications` (learn.microsoft.com/en-us/grap) and `servicePrincipals` (learn.microsoft.com/en-us/grap).

The Azure Portal knows `App Registrations` and `Enterprise Applications`.

App Registrations (Portal) = applications (Graph API)
Enterprise Applications (Portal) = servicePrincipals (Graph API)

Applications (App Registrations) and servicePrincipals (Enterprise Applications) have a unique, individual `ObjectId` but the ones that belong together hold the same `ApplicationId` which glues them together.

Fortunately, the Graph API documentation is clear and relatively consistent on what is expected for requesting an object - either the `objectId` or the `applicationId`:

```
GET /servicePrincipals/{id}
GET /servicePrincipals(appId='{appId}')
GET /applications/{applicationObjectId}
GET /applications(appId='{appId}')
```

When searching for servicePrincipals (Enterprise Applications) in the portal, it is not that clear since the terms are mixed up a bit.

#azure#graphapi#entraid