Authentication using Named & External Credential
Authentication is possible after a Named Credential is selected in the Filenize configuration screen. Use the Log In button in the configuration screen or in the Filenize component to start the authentication flow. After a successful authentication flow, the user is redirected back to the page where the user was before.
Pre 2.8: Authentication using Named Credential Legacy ( DEPRECATED)
With the creation of the Auth. Provider and Named Credential it is possible for each user to log in and use resources from SharePoint, this is required for each user that wants to work with Filenize. First, select your user at the top right, and click on “Settings” > “Authentication Settings for External Systems” > “New”. Provide the following information:
External System Definition: Named Credential
Named Credential: Your SharePoint Named Credential created earlier
User: Your user (This is automatically selected and readonly for non-admins)
Authentication Protocol: OAuth 2.0
Authentication Provider: Your SharePoint Auth. Provider created earlier
Start authentication Flow on Save: Checked
Upon saving, the Microsoft login screen is shown, after a successful login you can use Filenize with SharePoint.
Authenticated but still an error
From time to time, an error may be shown on the configuration page indicating that the user is not able to make a connection with SharePoint, even though the Authentication Settings for External System shows the status Authenticated. This can happen if the external user still has pending tasks to be completed. i.e. a password change. Always try to re-authenticate if this happens so you get prompted with the required tasks.
In addition, this can also occur if your service user is marked as a guest user in Azure. Make sure that your user is a member. Guest users can authenticate, but not use the underlying SharePoint API.
Microsoft Authentication error
During authentication, a prompt can be shown to indicate that the user does not have the correct permission. This can happen if access is limited for a set of users when using Conditional Access. This is not something Filenize can work around but can be evaluated in Azure. Please reach out to your Azure admin to diagnose the situation. (https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/troubleshoot-conditional-access#azure-ad-sign-in-events )
Add Comment