Microsoft.IdentityServer.Web.InvalidScopeException: MSIS7007: The requested relying party trust '' is unspecified or unsupported RRS feed

  • Question

  • We have an Asp. Net 3.5 website and we integrates with AD FS for some of our clients.

    For one of our clients production environment, the AD FS login screen is showing an error while login. The same AD FS login is working with same credential with their QA url. The login error message shows in the page is given below.

    There was a problem accessing the site. Try to browse to the site again.If the problem persists, contact the administrator of this site and provide the reference number to identify the problem.Reference number: f234fd22-ff72-41ad-bc27-99026b181b50

    From the Event Viewer log, the error message is:

    Exception details: Microsoft.IdentityServer.Web.InvalidScopeException: MSIS7007: The requested relying party trust ''is unspecified or unsupported. If a relying party trust was specified, it is possible that you do not have permission to access the trust relying party. Contact your administrator for details.

    Most of the online forums suggest to verify the Identifier of the Relying Party trust, which we already did.

    Please give some direction to identify the root cause behind this issue.

    Thank You,

    Sreekanth Mohan

    • Moved by 宝宝徐 Thursday, June 1, 2017 7:00 AM
    Tuesday, May 30, 2017 6:44 PM

All replies

  • Hi Screekanth,

    Thank you for posting in MSDN forum.

    This forum is about .Net Framework Setup and Servicing. As your question is much related to ADFS, I suggest you could post in Windows Server Active Directory Federation Services for a much professional and dedicated support.

    Thank you for your understanding and cooperation.

    Best Regards,

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Wednesday, May 31, 2017 5:22 AM