Unable to authenticate in 1.1.7RC1 : is it a regression?

[alex.kozlenkov]

Hi,

My previously working code is no longer functional in 1.1.7RC1. A fragment of the stack trace is given below

Caused by: java.lang.NoSuchMethodError: org.jboss.seam.security.Identity.addRole(Ljava/lang/String;)V
 at LoginAction.authenticate(LoginAction.java:70)
 at LoginAction$$FastClassByCGLIB$$92230edf.invoke(<generated>)
 at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
 at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:45)
 at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57)
 at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:34)
 at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
 at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:47)

I've verified that I am packaging the latest RC1 from the CVS repository. Any ideas about this behaviour?

Cheers--Alex

[fernando_jmt]

Could you paste your Authenticator class code.

I got the same error time ago, I would like to see if the code you have is similar.

[baz]

There are several changes.
1.
it is now
Identity.instance().addRole
instead of
Identity.addRole

2. the #{identity.login} returns now loggedIn instead of success

It is best to reread the new documentation and compare

[alex.kozlenkov]

Thanks for this help. It works now with the code below:

public boolean authenticate() {
 try {
 User user0 = (User) entityManager.createQuery(
 "from User where username = :username")
 .setParameter("username", Identity.instance().getUsername())
 .getSingleResult();
 if ( !compareHash( user0.getHashedPassword(), Identity.instance().getPassword() ) )
 {
 return false;
 }

 user = user0;

 if( user.getRoles() != null ) {
 for (UserRole r : user.getRoles())
 Identity.instance().addRole(r.getName());
 }
 return true;
 }
 catch (NoResultException ex) {
 log.warn("Invalid username/password");
 return false;
 }
 }

Can anyone clarify why it fails with identity injected via @In--it used to work before?
Thanks--Alex

[mariuszs]

Im using @In for Identity and this works for me very good.