[{"data":1,"prerenderedAt":81},["ShallowReactive",2],{"/2025/09/21-identityserver-authorizeattribute":3},{"id":4,"title":5,"body":6,"date":72,"description":69,"extension":73,"meta":74,"navigation":75,"path":76,"robots":77,"seo":78,"stem":79,"__hash__":80},"posts/2025/09/21 IdentityServer-AuthorizeAttribute.md","21 IdentityServer AuthorizeAttribute",{"type":7,"value":8,"toc":68},"minimark",[9,18,25,28,40,62],[10,11,13],"post-title",{":date":12},"date",[14,15,17],"h1",{"id":16},"identityserver-authorizeattribute","IdentityServer AuthorizeAttribute",[19,20,21],"notes",{},[22,23,24],"p",{},"This is a repost from my old blog. First posted in 11/10/2016.",[26,27],"br",{},[22,29,30,31,35,36,39],{},"I attempted to use ",[32,33,34],"code",{},"ResourceAuthorize"," attribute in my personal project which uses Thinktecture IdentityServer 3. When testing around, I suddenly realize not only ResourceAttribute is not working, the ",[32,37,38],{},"AuthorizeAttribute"," was broken as well. Spent hours testing and finally found out that it was caused by a slash (\"/\") at the end of my issuer.",[22,41,42,43,49,50,54,55,57,58,61],{},"So \"",[44,45,46],"a",{"href":46,"rel":47},"https://www.test.com/",[48],"nofollow","\" does not work, but \"",[44,51,52],{"href":52,"rel":53},"https://www.test.com",[48],"\" works somehow. The ",[32,56,38],{}," now works but at this time, I'm still checking why troubleshooting my ",[32,59,60],{},"ResourceAttribute",".",[22,63,64,65,67],{},"Edit: Apparently my ",[32,66,60],{}," was not working because one of the scopes is invalid and my intended scope is after that which eventually was not processed. And the requested claims will be included in the access_token.",{"title":69,"searchDepth":70,"depth":70,"links":71},"",2,[],"2025-09-21T00:00:00.000Z","md",{},true,"/2025/09/21-identityserver-authorizeattribute",null,{"title":5,"description":69},"2025/09/21 IdentityServer-AuthorizeAttribute","Onw5OwwFQ3pne3J-ydzEK-ZY7hxzIO9SfCsvSU_xxxw",1785167453093]