Silhouette is an authentication library for Play Framework applications that supports several authentication methods, including OAuth1, OAuth2, OpenID, Credentials or custom authentication schemes.
Can you please send me screenshots of your Heroku settings? to bravegag@gmail.com of course concealing any private/security/confidential data
@akkie @gobandoGH this is the log I am getting from Heroku https://www.dropbox.com/s/34k1lp36bxjq6xi/heroku.log?dl=0
Have you set the PLAY_CONF_FILE var to application.prod.conf?
@akkie this is my ProcFile
web: target/universal/stage/bin/myapp -Dhttp.port=${PORT} -Dconfig.file=${PLAY_CONF_FILE} -Dplay.evolutions.db.default.autoApply=true
and the
PLAY_CONF_FILE is set to application.prod.conf as part of the conf vars settings in Heroku
-Dconfig.resource
not
Dconfig.file
that was it :)
now I got other more reasonable errors
thank you!
@bravegag Your'e welcome! And many thanks for your contributions :+1:
If distributed, then a stateless authenticator. It's not easy to say if one or multiple authenticators should be used. Based on the assumption that you use different actions for your different application types, then: If you call a REST API from a mobile application than a token based authenticator would be a good fit. For a SPA or traditional web app, the cookie authenticator is great and has more advantages as a token based authenticator
The default fingerprint generator is based on browser headers and the remote address: https://github.com/mohiva/play-silhouette/blob/master/silhouette/app/com/mohiva/play/silhouette/impl/util/DefaultFingerprintGenerator.scala
From the doc:
The same with `Accept-Encoding`. But in Chromium/Blink based browser the content of this header may
be changed during requests. @see https://github.com/mohiva/play-silhouette/issues/277
Maybe this is the issue?
hi I saw the documentation about this dependency:
"com.mohiva" %% "play-silhouette-persistence-reactivemongo" % "6.0.0"
but it's not found, and I checked the github of play-silhouette-persistence-reactivemongo the version 6.0.0 is not release yet ?
anyone can help me ?
"com.mohiva" %% "play-silhouette-persistence-reactivemongo" % "6.0.0"
but it's not found, and I checked the github of play-silhouette-persistence-reactivemongo the version 6.0.0 is not release yet ?
anyone can help me ?
Hello guys.
We are trying to decode a Play JWT token on our other app in order to allow access on some specific resources and we are using https://github.com/jpadilla/pyjwt library. We are using the following code but we get Signature verification failed. Any suggestions?
jwt_payload = jwt.decode(token, 'changem', algorithms=['HS256'])
print(jwt_payload)jwt.exceptions.InvalidSignatureError: Signature verification failed
Hey guys, having trouble with the PasswordDAO migration to 6.1, could anyone help? Replied to a thread on forum: https://discourse.silhouette.rocks/t/problem-with-passwordinfodao-implmentation-in-silhouette-version-6-1/366/8
Hi guys I'm having a bit of an issue any help would be appreciated. Thought I would ask before filling a bug. Im using Play 2.7.3 play-silhouette 6.1.1 Guice and JWT. Im unable to to change authenticatorIdleTimeout to implement rememberMe. This code worked on play-silhouette 5.
case Some(user) => silhouette.env.authenticatorService.create(loginInfo).map {
case authenticator if data.rememberMe =>
val c = configuration.underlying
authenticator.copy(
expirationDateTime = clock.now + c.as[FiniteDuration]("silhouette.authenticator.rememberMe.authenticatorExpiry"),
idleTimeout = c.getAs[FiniteDuration]("silhouette.authenticator.rememberMe.authenticatorIdleTimeout"))
case authenticator => authenticator
}.flatMap { authenticator =>
silhouette.env.eventBus.publish(LoginEvent(user, request))
silhouette.env.authenticatorService.init(authenticator).map { token =>
Ok(Json.obj("token" -> token))
}
}Am I doing something wrong?
You say that the settings of the authenticator service has the remember me settings but that the generated token doesn't have the correct dates set? The
serialize function uses the dates from the authenticator when creating the token. So if you change the dates in the authenticator, then the token should also contain these dates. Have you double checked your new updated values and the exp and iat claims in your token? Are they not the same?
Christian, thank so much for taking time to help me out.
I see the code related to expirationDateTime and that works as expected. idleTimeout also makes makes it into the serialize. However, unserialize ignores authenticatorIdleTimeout and uses settings.authenticatorIdleTimeout
I see the code related to expirationDateTime and that works as expected. idleTimeout also makes makes it into the serialize. However, unserialize ignores authenticatorIdleTimeout and uses settings.authenticatorIdleTimeout
java.lang.NullPointerException: null
at com.mohiva.play.silhouette.impl.providers.SocialProvider$class.$init$(SocialProvider.scala:57)
at com.mohiva.play.silhouette.impl.providers.SocialProvider$class.$init$(SocialProvider.scala:57)