API fra Now Assist chat bot function til SharePoint
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hej,
Med Australia relase er der åbnet op for at Now Assist chat bot function kan bruge data fra andre sources end ServiceNow.
Når vi ønsker at sætte det op mod en SharePoint site skal NowAssist have fuld adgaing til SharePoint, hvilket vi ser som en security risk. Man kan lave det som read, men dermed kommer der fejl op ved konfigurering.
Det skyldes nok at NowAssist skal kunne verificere brugers adgang på SharePoint, så man ikke ser data der ikke er adgang til.
Andre som har erfaringer her?
/Karin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hej @kann
Synes det er et spændende emne ihverfald så følger lige med. Fordi det er ikke noget jeg kun oplever med SharePoint.
Hvis jeg var dig ville jeg prøve og snakke med en SharePoint administrator eller Microsoft også give feedback til ServiceNow eller en ServiceNow Partner om der er erfaring med om mindre roller kunne være vejen frem eller om det er nok at få adgangen i en begrænset periode for at mitigere security risk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hej Tommy,
En af vores udviklere har sendt en sag til ServiceNow og her var svaret, så ikke umiddelbart noget vi kan bruge.
Sites.FullControl.All
Sites.Selected
Sites.FullControl.All provides access across SharePoint Online and is the permission required if the connector needs to crawl sites without any additional site-specific configuration.
For customers who consider tenant-wide access to be too broad, the supported alternative is to use Sites.Selected. However, when using Sites.Selected, additional configuration is required as outlined in the following documentation:
Configure site and site collection access for the Microsoft SharePoint Online external content connector
With this approach, FullControl permissions are granted only on the specific SharePoint sites or site collections that should be crawled, rather than granting access across the entire tenant.
Regarding your question about using Read instead of FullControl, the connector requires FullControl when Sites.Selected is used because the connector needs to access SharePoint site metadata and associated information required for indexing operations. As a result, granting only Read permissions on the selected sites is not expected to provide the level of access required for the crawl to complete successfully.
Therefore, the behaviour you observed is expected:
Sites.Selected + FullControl on the specified SharePoint site(s) → Supported and expected to work.
Sites.Selected + Read on the specified SharePoint site(s) → Expected not to work for the connector crawl.
In summary, if tenant-wide Sites.FullControl.All permissions do not align with your security requirements, the recommended approach is to use Sites.Selected and grant FullControl only on the specific SharePoint sites or site collections that need to be indexed by the connector.
