Multiple different URL combinations based on online suggestions. If behind-the-scenes URI usage tends to encourage a near-equation of resource and representation, other aspects of sophisticated Web 2.0 usage tend in the opposite direction.
I can assure you that I am passing the correct token retrieved from the token request. Both URI and parameters are things which have to be specified as part of a web request, and this encourages the viewpoint that taken together they identify what is wanted. default: This gives me a successful response, however, whenever I try to make any request, including the basic read calendar request, I get InvalidAuthenticationToken. Since this works, I believe my other parameters are correct, and the scope is the problem. : This works for basic functions, like reading the calendar but I believe that the default permissions are very little for my needs. I have tried different parameters of the scope. I am certain that this scope parameter is the one causing me problems. I am trying to log in as my registered app, with the permissions granted on:Īzure Portal > App registrations > App registrations (Preview) > My App Name - API permissionsĪccording to this documentation, I have to pass my resource identifier ( APP ID URI) in the scope parameter when requesting a token.
0 kommentar(er)
