{"id":34088,"date":"2023-02-22T12:42:26","date_gmt":"2023-02-22T07:12:26","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=34088"},"modified":"2023-02-24T12:43:04","modified_gmt":"2023-02-24T07:13:04","slug":"authorize-multiple-resources-while-working-with-oauth2-request","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2023\/02\/authorize-multiple-resources-while-working-with-oauth2-request\/","title":{"rendered":"Authorize multiple resources while working with OAuth2 request"},"content":{"rendered":"

Recently, I had a requirement where I had to grant access to a user to use SharePoint as well as CRM using Azure App. While working on this, I came across an OAuth2 request that would allow us to get access tokens & refresh tokens using the scope of required resources (here, CRM & SharePoint).<\/p>\n

Since multiple scopes were being accepted, I went ahead and passed scopes of CRM SharePoint in the same request. The request was similar to the below –<\/p>\n

var b2cAuthUri = \"https:\/\/login.microsoftonline.com\/<\/a>\" + tenantId + \"\/oauth2\/v2.0\/authorize?\"+\r\n\r\n\"client_id=\" + clientId +\r\n\r\n\"&response_type=code\" +\r\n\r\n\"&redirect_uri=\" + redirectUrl +\r\n\r\n\"&scope=offline_access\"+\" \"+crmURL + \"\/user_impersonation\" +\" \"+ sharepointSite +\r\n\r\n\"\/User.read.all Sites.FullControl.All \" + \"\";<\/pre>\n
After the above request, I continued to perform operations according to the requirement. When I used the generated access token to perform CRM-related functionality it worked as expected. However, when I used the same access token to upload a file in SharePoint, it threw a 401 UNAUTHORIZED ERROR<\/strong><\/span>.<\/p>\n
Then after some digging, I found out that there is a restriction from the OAuth2 endpoint as it is designed to provide a token for the resource specified in the first scope listed in the request. This means that if a request is made with multiple scopes specified, only the first scope will be considered for token generation. As a result, any additional scopes listed in the request will not affect the token generation process.<\/p>\n
So, due to the restriction from OAuth2, I created a new request consisting of a single resource with a particular scope and generated the tokens using that request which worked as expected.<\/p>\n
Conclusion <\/strong><\/h2>\n
In the future, if you want to use multiple scopes and multiple resources, for each resource, a distinct request should be made that includes the request for that specific resource and its corresponding scope. By doing this, the requests can be tailored to meet the unique requirements of each resource and scope, providing greater control and flexibility in the request process.<\/p>\n
\"Assign<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Recently, I had a requirement where I had to grant access to a user to use SharePoint as well as CRM using Azure App. While working on this, I came across an OAuth2 request that would allow us to get access tokens & refresh tokens using the scope of required resources (here, CRM & SharePoint).\u2026 Read More: Authorize multiple resources while working with OAuth2 request »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[2675],"class_list":["post-34088","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-oauth2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t