{"id":37996,"date":"2017-01-03T19:17:24","date_gmt":"2017-01-03T13:47:24","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=37996"},"modified":"2017-01-05T09:33:14","modified_gmt":"2017-01-05T04:03:14","slug":"how-to-perform-event-on-successful-login-via-spring-security-in-grails","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/how-to-perform-event-on-successful-login-via-spring-security-in-grails\/","title":{"rendered":"How to Perform event on successful login via Spring Security in Grails"},"content":{"rendered":"

Some applications require to store and show last login of the user which is quite common. With this feature a user can verify the last login date and time upon successful login.<\/p>\n

I would like to explain this through a use case<\/strong> – One of the administrative application on Grails<\/a> required to hold last login date and time of the user, so that it can be shown to the user at the time of successful login.<\/p>\n

Problem:<\/strong> By default spring security does not provide such feature of capturing last login time. Moreover, we did not have such properties in our domain which could persist user specific last login information.<\/p>\n

Solution<\/b>: Fortunately Spring is quite flexible framework so it is not a big deal to achieve this.\u00a0Spring provides a authentication success listener which can perform specified action upon successful login of user<\/strong>.<\/p>\n

Hence with the help of following configurations we can store user\u2019s last login date time after successful authenticated login.<\/p>\n

    \n
  1. Add following field’s in your User domain :-<\/b><\/li>\n<\/ol>\n

    \u00a0\u00a0\u00a0 class User<\/p>\n

    \u00a0 {<\/p>\n

    \u00a0\u00a0\u00a0 Date lastLoginDate<\/p>\n

    \u00a0\u00a0\u00a0 Date currentLoginDate<\/p>\n

    \u00a0\u00a0 }<\/p>\n

      \n
    1. Add following configurations in your \/grails-app\/conf\/application.groovy (auto generated after installing Spring security Core plugin)<\/b><\/li>\n<\/ol>\n

      Enable your spring security events:-<\/p>\n

      grails.plugin.springsecurity.useSecurityEventListener = true<\/p>\n

      \/\/An event to be triggered after successful authentication and login of user.<\/b><\/p>\n

      Modify your spring security successful authentication events:-<\/p>\n

      grails.plugin.springsecurity.onInteractiveAuthenticationSuccessEvent = { e, appCtx -><\/p>\n

      User.withTransaction {<\/p>\n

      def user = User.findByIdAndIsDeleted(appCtx.springSecurityService.principal.id, false)<\/p>\n

      if (!user.isAttached())\/\/ Checks whether the domain instance is attached to a currently active Hibernate session.<\/p>\n

      user.attach()<\/p>\n

      user.lastLoginDate = user.currentLoginTime \/\/ update last login date<\/p>\n

      user.currentLoginDate = new Date() \/\/ update current login date<\/p>\n

      user.save(flush: true, failOnError: true)<\/p>\n

      }<\/p>\n

      }<\/p>\n

      Incase, you don’t need to retrieve the logged in user details, you can use<\/p>\n

      onAuthenticationSuccessEvent<\/b><\/p>\n

      3.\u00a0That’s it, its done!<\/b><\/p>\n

      Now use user.lastLoginDate to show last login time.<\/b><\/p>\n

      Similarly, we can call an event on AuthenticationFailure\/Unsuccessful Login via AbstractAuthenticationFailureEvent:<\/b><\/p>\n

      \/\/An event to be triggered on AuthenticationFailure\/Unsuccessful Login of user.<\/b><\/p>\n

      grails.plugin.springsecurity.onAbstractAuthenticationFailureEvent = { event, appCtx -><\/p>\n

      \/\/ Action to be performed (Example : send e-mail)<\/p>\n

      }<\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      Some applications require to store and show last login of the user which is quite common. With this feature a user can verify the last login date and time upon successful login. I would like to explain this through a use case – One of the administrative application on Grails required to hold last login […]<\/p>\n","protected":false},"author":685,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":29},"categories":[2026,7,1],"tags":[2270,4840,4841,672],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/37996"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/685"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=37996"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/37996\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=37996"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=37996"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=37996"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}