{"id":132,"date":"2009-06-08T09:07:01","date_gmt":"2009-06-08T13:07:01","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/?p=132"},"modified":"2009-06-22T15:15:41","modified_gmt":"2009-06-22T19:15:41","slug":"preview-amazon-s3-integration-dodnn-conference","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/2009\/06\/08\/preview-amazon-s3-integration-dodnn-conference\/","title":{"rendered":"Preview: Amazon S3 Integration @ the DoDNN Conference"},"content":{"rendered":"<p>As many are aware, I will be presenting a session at the upcoming <a href=\"http:\/\/dayofdnn.com\/\">Day of DotNetNuke<\/a> conference in Orlando, Florida. \u00a0The session is entitled &#8220;<a href=\"http:\/\/dayofdnn.com\/Sessions\/tabid\/214\/CodecampId\/1\/SessionId\/33\/Default.aspx\">The Cutting Edge: Advanced Authorization in DotNetNuke 5.1<\/a>.&#8221; \u00a0The abstract for this session reads:<\/p>\n<blockquote><p>Among the many improvements present in DotNetNuke version 5.1, this latest release includes authorization as a first-class extension point. \u00a0This allows customization previously impossible without core modification. \u00a0Additionally, the permission model (and the internal use thereof) has been significantly streamlined and centralized, allowing for great flexibility across myriad use scenarios.<\/p>\n<p>In this session, we explore the new permission provider in detail. \u00a0This includes a discussion of how (and why) authorization services were centralized and abstracted, the overall design and structure of the provider, and available points of access control. \u00a0Finally, we examine some concrete ways in which the provider might be extended to meet real-world policy requirements.<\/p><\/blockquote>\n<p>When presenting architectural or theoretical material, I always strive to include a demonstration of how the material might be applied to a real-world scenario. \u00a0In this case, I will be demonstrating how a custom authorization provider can be used to enable full DotNetNuke integration with cloud-based <a href=\"http:\/\/aws.amazon.com\/s3\/\">Amazon S3 webservices<\/a>. \u00a0A screenshot of the file manager in an Amazon S3-enabled installation is displayed below.<\/p>\n<div style=\"float: right;margin: 8px\"><a href=\"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/files\/2009\/06\/amazon-s3-teaser.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-46\" src=\"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/files\/2009\/06\/amazon-s3-teaser-300x167.png\" alt=\"A screenshot demonstrating Amazon S3 cloud-based integration on the DotNetNuke platform\" width=\"300\" height=\"167\" \/><\/a><\/div>\n<p>This session should appeal to a wide audience; I cover enough theoretical background for individuals new to security theory, and delve deep enough into the 5.1 authorization architecture to satisfy those that have high familiarity with the platform. \u00a0If you are interested in learning more about the internals of the framework &#8212; and how 5.1 authorization might be utilized &#8212; be sure to stop by!<\/p>\n<p>Epilogue: The presentation materials are now <a href=\"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/2009\/06\/16\/presentation-materials-advanced-authorization-in-dotnetnuke\/\">available here<\/a>, and the Amazon S3 Integration providers may be <a href=\"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/2009\/06\/22\/released-dotnetnuke-amazon-s3-folder-integration-providers\/\">found here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As many are aware, I will be presenting a session at the upcoming Day of DotNetNuke conference in Orlando, Florida. \u00a0The session is entitled &#8220;The Cutting Edge: Advanced Authorization in DotNetNuke 5.1.&#8221; \u00a0The abstract for this session reads: Among the many improvements present in DotNetNuke version 5.1, this latest release includes authorization as a first-class [&hellip;]<\/p>\n","protected":false},"author":1933,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3062,6152],"tags":[6154,6153,3070,19470,6155,593,19469],"class_list":["post-132","post","type-post","status-publish","format-standard","hentry","category-dotnetnuke-dnn-content-management-system","category-security-technology","tag-6154","tag-authorization","tag-dotnetnuke","tag-dotnetnuke-dnn-content-management-system","tag-dotnetnuke-51","tag-security","tag-technology"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/users\/1933"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/comments?post=132"}],"version-history":[{"count":23,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/132\/revisions"}],"predecessor-version":[{"id":155,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/132\/revisions\/155"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/media?parent=132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/categories?post=132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/tags?post=132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}