Nextcloud & Entra ID SAML SSO Problem

Min Kyo Chung 0 Reputation points
2024-04-15T08:02:11.5433333+00:00

I would like to connect to Nextcloud using Entra ID's enterprise application SSO authentication function.

I succeeded in popping up the login screen by referring to the posted guides.

User's image

However, when I try to log in with the entra ID account, (User permissions have been granted)

test1

AADSTS70016 error is displayed as shown in the image.

But the question here is, The image above says ‘Application with identifier http://domian.com/index.php/apps/user_saml/saml/metadata was not found in directory’.

But I have set Identifier and Reply URL as below

TEST2

Both Identifier and Reply URL are setting in https format.

TEST3

TEST4

The manifest is also set to https format.

I am curious as to why it keeps saying that the http://domian.com Identifier cannot be found despite the settings being like this.

To solve this problem, I deleted the Enterprise Application I had created and re-created it. But the result was the same.

Please let me know how to solve it. Thank you.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,521 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Navya 4,000 Reputation points Microsoft Vendor
    2024-04-16T15:51:54.9333333+00:00

    Hi @Min Kyo ChungThank you for posting this in Microsoft Q&A.

    The error message "Application with identifier http://domian.com/index.php/apps/user_saml/saml/metadata was not found in directory" indicates that the identifier you have configured for your Nextcloud application in Azure AD does not match the identifier that is being sent in the SAML request.

    To resolve this issue, you can try the following steps:

    1. Double-check the identifier and reply URL that you have configured for your Nextcloud application in Azure AD. Make sure that they match the values that are being sent in the SAML request.
    2. Check if the identifier and reply URL are using the correct protocol (http or https). If your Nextcloud instance is using https, make sure that the identifier and reply URL are also using https.
    3. Verify that the SAML metadata URL for your Nextcloud instance is correct and accessible. You can try accessing the metadata URL directly in your browser to see if it returns the correct metadata.

    Hope this helps. Do let us know if you any further queries.

    Thanks,

    Navya.

    0 comments