External User Unable to Log In Due to Azure AD SSO Redirect
Original Question or Issue:
A newly created external user was unable to log in to FileCloud and received an Azure AD error stating that access to the FileCloud application was blocked.
Environment:
- Product - FileCloud Server
- Version - 23.261
- Platform - Linux,
Steps to Reproduce:
-
Create or invite a new external user.
-
User attempts to access FileCloud through the standard login page.
-
Browser redirects the user to Microsoft Entra ID (Azure AD) authentication
-
User receives an access denied error and cannot log in.
Error or Log Message:
AADSTS50105: Your administrator has configured the application FileCloud to block users unless they are specifically granted access to the application.The signed in user is blocked because they are not a direct member of a group with access, nor had access directly assigned by an administrator.
Defect or Enhancement Number:
Cause:
The organization uses Single Sign-On (SSO) for internal users only. The external user was inadvertently being redirected through the SSO authentication flow, resulting in an Azure AD access error because the user was not assigned access to the FileCloud Enterprise Application.
Resolution or Workaround:
- Have the external user bypass the SSO flow and log in directly using FileCloud credentials:
- Right-click the Chrome browser icon.
- Select New Incognito Window.
- Open the following URL:
https://<your-filecloud-url>/ui/core/index.html#/
- Log in using the FileCloud username and password instead of SSO.
The external user was able to successfully log in using this method.
Notes:
-
This issue occurred because SSO is intended only for internal users.
-
Using an Incognito window prevents existing Azure AD sessions from automatically redirecting the user to SSO.
-
If external users are not intended to use SSO, direct FileCloud authentication should be used instead.