Will this sample and pattern work with On Prem ADFS on 2016?
redshiftz opened this issue · 5 comments
Will this sample and pattern work with On Prem ADFS on 2016? I've been trying for days and getting "MSIS9602: The received 'resource' parameter is invalid. The authorization server can not find a registered resource with the specified identifier."
Thank you.
did you follow any specific guidance. I'd recommend https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/enabling-oauth-confidential-clients-with-ad-fs.
I've been trying to follow this...
https://azure.microsoft.com/en-us/resources/samples/active-directory-dotnet-native-headless/
but keep getting "MSIS9602: The received 'resource' parameter is invalid. The authorization server can not find a registered resource with the specified identifier." when making the initial AcquireTokenAsync with UserCredential.
The url you provided doesn't seem to allow for headless usage which is our use case. We have external customers that have server software that needs to authenticate using OAUTH OpenId Connect using username and password. Then they are allowed to request data filtered to their login via claims.
@redshiftz : can you please tell us more about your resource (called Web API). did you register your application with https://portal.azure.com ? (is it a V1 resource)?
The sample should work. I have a .NET 4.7.1 console app inspired by the sample.
Can you describe how you configured your application group?
The error message to me indicates that the resource in your authorisation request is not the same as the identifier of your web api.
Closing this issue as we think it's a configuration issue (confirmed by Technicalli who has it working)