Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 27 17:45
    rorygraves commented #569
  • Feb 27 16:39

    akkie on gh-pages

    updated site (compare)

  • Feb 27 16:33

    akkie on gh-pages

    updated site (compare)

  • Feb 27 16:30
    akkie closed #569
  • Feb 27 16:30
    akkie commented #569
  • Feb 27 16:28

    akkie on 7.0.0

    (compare)

  • Feb 27 16:25

    akkie on master

    Release version 7.0.0 (compare)

  • Feb 10 19:05
    akkie commented #569
  • Feb 10 19:04

    akkie on 7.0.0-RC1

    (compare)

  • Feb 10 19:04

    akkie on 7.0.0-RC1

    (compare)

  • Feb 10 19:01

    akkie on 7.0.0-RC1

    Release version 7.0.0-RC1 (compare)

  • Feb 10 18:53

    akkie on gh-pages

    updated site (compare)

  • Feb 10 18:51

    akkie on gh-pages

    updated site (compare)

  • Feb 10 18:47

    akkie on gh-pages

    updated site (compare)

  • Feb 10 18:38

    akkie on master

    Release version 7.0.0-RC1 (#577) (compare)

  • Feb 10 18:38
    akkie closed #577
  • Feb 10 16:57
    coveralls commented #577
  • Feb 10 16:57
    coveralls commented #577
  • Feb 10 16:46
    akkie opened #577
  • Feb 10 10:02

    akkie on gh-pages

    updated site (compare)

Giovanni Azua
@bravegag
that was it :)
now I got other more reasonable errors
thank you!
Christian Kaps
@akkie
@gobandoGH Yes, this makes sense. But note, that Silhouette supports also a stateless variant of the CookieAuthenticator.
@bravegag Your'e welcome! And many thanks for your contributions :+1:
Giovanni Azua
@bravegag
@akkie Happy to help!
gobandoGH
@gobandoGH
Thank you @akkie. What would be your recommendation for a single authenticator to attend both web/mobile authentication requests looking forward to a distribute deployment scenario ?
Christian Kaps
@akkie
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
gobandoGH
@gobandoGH
Thank you @akkie !
Vinicius Miana
@ViniciusMiana
Hello, I made a small change on the LinkedInProvider, since the v1 resources are no longer available. Can I just open a PR or do you need anything else?
Vinicius Miana
@ViniciusMiana
Here is the PR: mohiva/play-silhouette#568
lasimon
@lasimon
I have an e2e test (Cypress) that runs fine with a Play app using Silhouette when it runs on my laptop but throws a "Fingerprint doesn't match authenticator" when run against the same app in production. Any ideas what to look at/try?
Christian Kaps
@akkie
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?
adilkurniaramdan
@adilkurniaramdan
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 ?
Christian Kaps
@akkie
Yes, it's not released. You could create a PR for Play 2.7 to make it work
Georgios Larkou
@glarkou

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
Georgios Larkou
@glarkou
We solved it. Don't worry!
Ender-Wiggin
@Ender-Wiggin
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
asedghi
@asedghi

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?

Christian Kaps
@akkie
What exactly is the issue?
asedghi
@asedghi
So i can set authenticatorIdleTimeout in configuration at startup and it works fine. However if I set the same setting during user login it does nothing. the authenticatorIdleTimeout stays the same.
asedghi
@asedghi
I've also debug the code and can see that authenticator has the updated settings from remember me when it call authenticatorService.init(authenticator) .
asedghi
@asedghi
The issue for me is purely with JWT. Cookie auth works as expected.
Christian Kaps
@akkie
Remember me was only planned for cookies. Does it work with JWT in the previous version?
asedghi
@asedghi
its documented as "Can be used for remember me functionality" and is used in play-silhouette-angular-typescript.g8 looks like the last working version was 5.0.3. the code example above was from that code
Christian Kaps
@akkie
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?
asedghi
@asedghi
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
asedghi
@asedghi
I also see where iat and exp are set but It looks like idletimeout is entirely ignored. in the serialize method
Christian Kaps
@akkie
Yes, the idleTimeout is currently not stored in the JWT. We could introduce a new reserved claim idt and set the idle timeout during serialization. So we can extract it from the JWT during unserialization. Would you create a PR containing these changes with also some tests?
asedghi
@asedghi
Sure, should be simple enough. I'll take a stab at it over the weekend.
@ugobourdon
@ubourdon
Hi. Where can i find an example using OpenIDProvider ?
@ugobourdon
@ubourdon
Hi. When try to instanciate OpenIdProvider i have this error :
java.lang.NullPointerException: null
at com.mohiva.play.silhouette.impl.providers.SocialProvider$class.$init$(SocialProvider.scala:57)
Have you ever seen this ?
@ugobourdon
@ubourdon
ok thx. I'll go there to append more details
nafg
@nafg
This message was deleted
@ugobourdon
@ubourdon
@akkie Have you been able to reproduce reproduce my issue ? I really don't know how to do to instanciate my Provider ...
Aidar
@SunPj
Hi. I have prepared VueJs + Silhouette sample. Demo is on heroku https://vuejs-slihouette.herokuapp.com/
Github repo is https://github.com/SunPj/silhouette-vuejs-app
Hope someone can find that useful. I would be happy if you add it among samples in Silhouette website. Thanks
Christian Kaps
@akkie
@SunPj you can add a suggested edit on the website
Aidar
@SunPj
Thanks @akkie . Will do
neimspace11
@neimspace11

Hi @SunPj , thanks for creating VueJs + Silhouette sample. I have tried to build & run it locally, however receiving this error when trying to open localhost:9000:

No configuration setting found for key 'silhouette.csrfStateItemHandler.signer.key' at modules.SilhouetteModule.provideCSRFStateItemSigner(SilhouetteModule.scala:179)

Any ideas what I am missing ?

neimspace11
@neimspace11
@SunPj Nevermind the above question, as I sorted out myself (changing ENV variable did the trick).
Aidar
@SunPj
Hi @neimspace11 Sorry to hear that. There are some conf params that are wired to ENV pararms. Happy to hear that you solved the issue. Let me know if you have any questions.
neimspace11
@neimspace11

@SunPj Thank you for response. So I managed to launch the app on localhost:8080, however when trying to submit sign-in or registration I am receiving HTTP status code - 404 Not Found on front-end part (on backend app I don't receive any error logs)

POST http://localhost:8080/signIn 404

As backend is running on port :9000, could it be that some routing between front-end and backend is missing here.

Aidar
@SunPj
Hi @neimspace11 You should run both apps but use :9000 on your browser. Frontend part will be proxied by backend
neimspace11
@neimspace11

Yes, I just tried and I am receiving 500 Internal Server error
On backend part, the error logs are as following:

[error] a.a.ActorSystemImpl - Internal server error, sending 500 response
akka.http.impl.util.One2OneBidiFlow$OutputTruncationException: Inner flow was completed without producing result elements for 1 outstanding elements
at akka.http.impl.util.One2OneBidiFlow$OutputTruncationException$.apply(One2OneBidiFlow.scala:22)
at akka.http.impl.util.One2OneBidiFlow$One2OneBidi

KaTeX parse error: Can't use function '$' in math mode at position 5: anon$̲1: anon$1
anon$4.onUpstreamFinish(One2OneBidiFlow.scala:97)
at akka.stream.impl.fusing.GraphInterpreter.processEvent(GraphInterpreter.scala:506)

Any ideas what could be wrong