search

joscha / play-authenticate

An authentication plugin for Play Framework 2.x (Java)
http://joscha.github.com/play-authenticate/
Other
807 stars 367 forks source link

No custom TemplateFailureListener found #283

Closed slimandslam closed 8 years ago

slimandslam commented 8 years ago

When I run my Play app (Play v2.4.3) on my laptop, everything is fine, but on a remote server, I get this cryptic message and the play-authenticate auth does not work:

2015-09-15 15:18:59 +0000 [INFO] from play.api.Play in main - Application started (Prod)
2015-09-15 15:19:00 +0000 [INFO] from play.core.server.NettyServer in main - Listening for HTTP on /0:0:0:0:0:0:0:0:9000
2015-09-15 15:19:00 +0000 [INFO] from play.core.server.NettyServer in main - Listening for HTTP on /0:0:0:0:0:0:0:0:9000
2015-09-15 15:19:09 +0000 [INFO] from be.objectify.deadbolt.java.TemplateFailureListenerProvider in application-akka.actor.default-dispatcher-2 - No custom TemplateFailureListener found, falling back to no-op implementation
2015-09-15 15:19:09 +0000 [INFO] from be.objectify.deadbolt.java.ViewSupport in application-akka.actor.default-dispatcher-2 - Default timeout period for blocking views is [130000]ms

I tried changing my deadbolt.conf file to this, but it didn't make any difference:

deadbolt {
  java {
    blocking = true # JPA doesn't support non-blocking
    cache-user = true # For the rest of the request
    handler = auth.MyDeadboltHandler
    view-timeout=130000 # Default 1000
    blocking-timeout=2000
  }
}

My build.sbt file has these two lines:

 "be.objectify"  %% "deadbolt-java"     % "2.4.2.1",
  "com.feth" %%  "play-authenticate" % "0.7.0-SNAPSHOT",
slimandslam commented 8 years ago

This was not the issue. Closing.