![]() Join our public community call series on May 18 th: Check out our platform community calls section for more information. Check Migrate to the Microsoft Authentication Library (MSAL) for guidance and this blog post from Den Delimarsky for details. ![]() Go to ADFS management console -> RPT (Relaying Party) ->Microsoft office 365 identity platform " -> Edit claims rules or Edit issuance authorization rules.Check out this post: Scope App Permissions for Secure Automation using Microsoft Azure Active Directory and watch for other great content coming to our blog!ĪDAL Deprecation: ADAL end of life is now June 30, 2023, no support or security fixes will be provided past end-of-life, so prioritize migration to Microsoft Authentication Library (MSAL). I have been through a number of the article linked but I cannot see the below being set anywhere. I suspect this is because I did not let Azure AD Connect interact with my ADFS environment and was therefore unable to update the claim settings with "default" settings. It seems the claim rules setup on my implementation was not correct and I was getting the same issue. ![]() Not sure if it is going to help but had to follow the below steps provided by Microsoft Support last week. Could this be the difference that is causing our configuration to not work with the Partner site but work otherwise? (it is mainly missing the "c:" before type and not using the secure URL's).Ĭ: => issue(Type = " ", Value = " ")ĪdditionalAuthenticationRules : exists([Type = I have been through those articles and can see a difference between my configuration (which is working for granting user access to resources, including the Partner Site) and those articles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |