![]() ![]() It is the Sophos Plugin running on the Partners Server that is the source of the request. These are entries made by your Partner's RMM applications that utilize our Sophos plug-in/Management APIs. Please whitelist the IP addresses from the Europe region: Ĭentral Dashboard Audit Logs: repeated "Access Denied" entries referencing 'alerts:read' and 'endpoint-state:read'Ĭustomers (Central Dashboard and Enterprise Dashboard), as well as Partners (Partner Dashboard) - could see excess amounts of Audit log entries that reference both 'alerts:read' and 'endpoint-state:read'. This requires customers on-premise IDP server to be able to communicate with Auth0’s servers. Sophos Federation login utilizes Auth0 as a third-party proxy service for integration with different IDP providers. One common reason for these errors is a result of customers' local IDP server being behind a firewall with regional restrictions that is preventing communication with Auth0 services hosted in Europe. (Okta) Attempting to log in via SSO you receive an "Expected 200 OK, got: 403 Forbidden" error (ADFS) "Failed to change IDP status" error attempting to add a new Identity Provider configuration. The nested groups are associated, but they are not visible, and any policy applied to the top group will still propagate to the appropriate subgroups.Ĭentral Federation login: "Failed to change IDP status" or "Expected 200 OK, got: 403 Forbidden" errors ![]() There is a known behavior when selecting an Azure AD sync’d group within the People > Groups section:Īny Azure sync’d group that has sub/nested groups within it, will still show '0' groups within it, in the UI. Azure AD sync: Nested groups will not be shown in the group modal
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |