5. Login to SharePoint in Salesforce (all users)
- Daniël Loriaux
- Henk-Jan van der Bijl
Authentication using Named & External Credential
Authentication becomes possible after selecting a Named Credential in the Filenize configuration screen. To begin the authentication flow, simply use the "Log In" button within the configuration screen or in the Filenize component.
Once the authentication flow is successfully completed, the user is redirected back to the page they were on before initiating the authentication process. This seamless process allows users to connect with their designated Named Credential securely and efficiently.
Authentication using Named Credential Legacy ( DEPRECATED)
After creating the Auth. Provider and Named Credential, each user can now log in and access resources from SharePoint. To enable this for each user using Filenize, follow these steps:
Select your user at the top right of the screen and click on "Settings" > "Authentication Settings for External Systems" > "New."
Provide the following information:
External System Definition: Named Credential
Named Credential: Select your SharePoint Named Credential created earlier
User: Your user (This is automatically selected and read-only for non-admins)
Authentication Protocol: OAuth 2.0
Authentication Provider: Select your SharePoint Auth. Provider created earlier
Start Authentication Flow on Save: Check this option
Upon saving, the Microsoft login screen will be displayed. After a successful login, you can use Filenize with SharePoint. This enables seamless access to SharePoint resources for each user in your organization.
Authenticated but still an error
From time to time, you may encounter an error on the configuration page indicating that the user is unable to establish a connection with SharePoint, even though the Authentication Settings for External System shows the status as Authenticated. This situation can occur if the external user has pending tasks that need to be completed, such as a password change or other authentication requirements. If this happens, it's advisable to try re-authenticating to prompt the user with the required tasks.
Additionally, this issue may arise if your service user is marked as a guest user in Azure. To resolve this, ensure that your user is a member rather than a guest. Guest users can authenticate, but they may not have access to use the underlying SharePoint API, leading to the connection issue. By ensuring the user is a member, you can overcome this challenge and ensure smooth communication between Filenize and SharePoint.
Microsoft Authentication error
During the authentication process, a prompt may appear indicating that the user does not have the correct permission. This can occur if access is restricted for a specific set of users when using Conditional Access. Unfortunately, Filenize cannot work around this limitation directly. However, the issue can be evaluated and addressed in Azure.
To diagnose the situation and resolve any Conditional Access-related problems, it is recommended to reach out to your Azure admin. They can investigate the Azure AD sign-in events and identify the specific conditions causing the access restrictions. By working together with your Azure admin, you can ensure that the necessary permissions and configurations are in place to enable smooth authentication and seamless usage of Filenize with SharePoint. (https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/troubleshoot-conditional-access#azure-ad-sign-in-events )