{"id":5447,"date":"2012-05-03T14:25:42","date_gmt":"2012-05-03T08:55:42","guid":{"rendered":"https:\/\/2thenew.today\/blog\/?p=5447"},"modified":"2016-12-19T14:36:46","modified_gmt":"2016-12-19T09:06:46","slug":"restricting-access-to-plugins-classes-with-spring-security","status":"publish","type":"post","link":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/","title":{"rendered":"Restricting Access To Plugin&#8217;s Classes With Spring Security"},"content":{"rendered":"<p>Many of Grails plugin like  searchable \u00a0and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my  project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There  are many ways of restricting access like doing it manually in filters. But since I am using spring security plugin, there was a better way out. It allows to create mapping (static rules) as configuration for different user roles.<\/p>\n<p>There are different ways of securing url in spring security plugin. And since I am using annotations, I&#8217;ll be defining static rule for annotations only.<\/p>\n<p>[java]<\/p>\n<p>grails.plugins.springsecurity.controllerAnnotations.staticRules = [<\/p>\n<p>&#8216;\/console\/**&#8217;: [&#8216;ROLE_ADMIN&#8217;],<\/p>\n<p>&#8216;\/searchable\/**&#8217;: [&#8216;ROLE_ADMIN&#8217;]<\/p>\n<p>]<\/p>\n<p>[\/java]<\/p>\n<p>By doing this I blocked access for all but ones with the role &#8220;ROLE_ADMIN&#8221; \u00a0for console and searchable controllers.<\/p>\n<div>_________________________________<\/div>\n<div>Hitesh Bhatia<br \/>\nMail,LinkedIn,<a href=\"http:\/\/www.facebook.com\/home.php?#%21\/profile.php?id=100000114437286\" target=\"_blank\">Facebook<\/a>,<a href=\"http:\/\/twitter.com\/d1_ricky\" target=\"_blank\">Twitter<\/a><br \/>\n_________________________________<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Many of Grails plugin like searchable \u00a0and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways [&hellip;]<\/p>\n","protected":false},"author":16,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2,"footnotes":""},"categories":[7],"tags":[350,813,812,326,672,811],"class_list":["post-5447","post","type-post","status-publish","format-standard","hentry","category-grails","tag-annotations","tag-console","tag-mapping","tag-searchable","tag-spring-security","tag-static-roles"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Hitesh Bhatia\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"TO THE NEW BLOG\" \/>\n\t\t<meta property=\"og:type\" content=\"blog\" \/>\n\t\t<meta property=\"og:title\" content=\"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog\" \/>\n\t\t<meta property=\"og:description\" content=\"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary\" \/>\n\t\t<meta name=\"twitter:site\" content=\"@tothenew\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#article\",\"name\":\"Restricting Access To Plugin\\u2019s Classes With Spring Security | TO THE NEW Blog\",\"headline\":\"Restricting Access To Plugin&#8217;s Classes With Spring Security\",\"author\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/author\\\/hitesh\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/#organization\"},\"datePublished\":\"2012-05-03T14:25:42+05:30\",\"dateModified\":\"2016-12-19T14:36:46+05:30\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#webpage\"},\"articleSection\":\"Grails, Annotations, console, mapping, searchable, spring security, static roles\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.tothenew.com\\\/blog\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/category\\\/grails\\\/#listItem\",\"name\":\"Grails\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/category\\\/grails\\\/#listItem\",\"position\":2,\"name\":\"Grails\",\"item\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/category\\\/grails\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#listItem\",\"name\":\"Restricting Access To Plugin&#8217;s Classes With Spring Security\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#listItem\",\"position\":3,\"name\":\"Restricting Access To Plugin&#8217;s Classes With Spring Security\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/category\\\/grails\\\/#listItem\",\"name\":\"Grails\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/#organization\",\"name\":\"TO THE NEW Blog\",\"url\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/author\\\/hitesh\\\/#author\",\"url\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/author\\\/hitesh\\\/\",\"name\":\"Hitesh Bhatia\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/480688fa251da2d21002803e0b349c1fe911842715b972676a1aa3cb12808e58?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Hitesh Bhatia\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#webpage\",\"url\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/\",\"name\":\"Restricting Access To Plugin\\u2019s Classes With Spring Security | TO THE NEW Blog\",\"description\":\"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/restricting-access-to-plugins-classes-with-spring-security\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/author\\\/hitesh\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/author\\\/hitesh\\\/#author\"},\"datePublished\":\"2012-05-03T14:25:42+05:30\",\"dateModified\":\"2016-12-19T14:36:46+05:30\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/\",\"name\":\"TO THE NEW Blog\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.tothenew.com\\\/blog\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog","description":"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways","canonical_url":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#article","name":"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog","headline":"Restricting Access To Plugin&#8217;s Classes With Spring Security","author":{"@id":"https:\/\/2thenew.today\/blog\/author\/hitesh\/#author"},"publisher":{"@id":"https:\/\/2thenew.today\/blog\/#organization"},"datePublished":"2012-05-03T14:25:42+05:30","dateModified":"2016-12-19T14:36:46+05:30","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#webpage"},"isPartOf":{"@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#webpage"},"articleSection":"Grails, Annotations, console, mapping, searchable, spring security, static roles"},{"@type":"BreadcrumbList","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog#listItem","position":1,"name":"Home","item":"https:\/\/2thenew.today\/blog","nextItem":{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog\/category\/grails\/#listItem","name":"Grails"}},{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog\/category\/grails\/#listItem","position":2,"name":"Grails","item":"https:\/\/2thenew.today\/blog\/category\/grails\/","nextItem":{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#listItem","name":"Restricting Access To Plugin&#8217;s Classes With Spring Security"},"previousItem":{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#listItem","position":3,"name":"Restricting Access To Plugin&#8217;s Classes With Spring Security","previousItem":{"@type":"ListItem","@id":"https:\/\/2thenew.today\/blog\/category\/grails\/#listItem","name":"Grails"}}]},{"@type":"Organization","@id":"https:\/\/2thenew.today\/blog\/#organization","name":"TO THE NEW Blog","url":"https:\/\/2thenew.today\/blog\/"},{"@type":"Person","@id":"https:\/\/2thenew.today\/blog\/author\/hitesh\/#author","url":"https:\/\/2thenew.today\/blog\/author\/hitesh\/","name":"Hitesh Bhatia","image":{"@type":"ImageObject","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/480688fa251da2d21002803e0b349c1fe911842715b972676a1aa3cb12808e58?s=96&d=mm&r=g","width":96,"height":96,"caption":"Hitesh Bhatia"}},{"@type":"WebPage","@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#webpage","url":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/","name":"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog","description":"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/2thenew.today\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/#breadcrumblist"},"author":{"@id":"https:\/\/2thenew.today\/blog\/author\/hitesh\/#author"},"creator":{"@id":"https:\/\/2thenew.today\/blog\/author\/hitesh\/#author"},"datePublished":"2012-05-03T14:25:42+05:30","dateModified":"2016-12-19T14:36:46+05:30"},{"@type":"WebSite","@id":"https:\/\/2thenew.today\/blog\/#website","url":"https:\/\/2thenew.today\/blog\/","name":"TO THE NEW Blog","inLanguage":"en-US","publisher":{"@id":"https:\/\/2thenew.today\/blog\/#organization"}}]},"og:locale":"en_US","og:site_name":"TO THE NEW BLOG","og:type":"blog","og:title":"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog","og:description":"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways","og:url":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/","og:image":"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png","og:image:secure_url":"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png","twitter:card":"summary","twitter:site":"@tothenew","twitter:title":"Restricting Access To Plugin\u2019s Classes With Spring Security | TO THE NEW Blog","twitter:description":"Many of Grails plugin like searchable and console can prove to be really dangerous if access to their URLs is not blocked. After adding searchable plugin to my project, I realized that access to its controllers was not defined and was open for all. Now this was a major security concern. There are many ways","twitter:image":"https:\/\/2thenew.today\/blog\/wp-content\/themes\/ttn\/images\/social-logo.png"},"aioseo_meta_data":{"post_id":"5447","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"limit_modified_date":false,"created":"2021-04-30 03:11:04","updated":"2024-02-29 09:36:21","focus_keyword":null,"additional_keywords":null,"truseo_locale":null,"ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/2thenew.today\/blog\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/2thenew.today\/blog\/category\/grails\/\" title=\"Grails\">Grails<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tRestricting Access To Plugin\u2019s Classes With Spring Security\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/2thenew.today\/blog"},{"label":"Grails","link":"https:\/\/2thenew.today\/blog\/category\/grails\/"},{"label":"Restricting Access To Plugin&#8217;s Classes With Spring Security","link":"https:\/\/2thenew.today\/blog\/restricting-access-to-plugins-classes-with-spring-security\/"}],"_links":{"self":[{"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/posts\/5447","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/comments?post=5447"}],"version-history":[{"count":0,"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/posts\/5447\/revisions"}],"wp:attachment":[{"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/media?parent=5447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/categories?post=5447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/2thenew.today\/blog\/wp-json\/wp\/v2\/tags?post=5447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}