1 Reply Latest reply on Dec 8, 2008 11:24 AM by Eric H

    Tricky problem with Seam 2.1 identity management

    Eric H Novice

      I happily defined my user entity with a field like this:


          @UserPassword
          public String getPassword() {
              return password;
          }



      Readiong the API docs on the @UserPassword annotation, it clearly says that the has attribute is optional, so I left it out, because I don't want it hashed.


      This doesn't work.


      Gotta have:


          @UserPassword(hash="none")
          public String getPassword() {
              return password;
          }



      if you want no hash.


      Took me a while to figure that out.