Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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)

  • Feb 10 09:54

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:52

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:49

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:46

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:41

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:38

    akkie on gh-pages

    updated site (compare)

  • Feb 10 09:30
    akkie commented #576
Christian Kaps
@akkie
As noted in a previous post. In the current version of Silhouette, only one authenticator can be used per action. If you have different actions for your mobile app, you can use whatever authenticatior you want. If the actions should be used for multiple apps, then it's a bit more complicated.
Albaro Pereyra
@AlbaroPereyra
For apps I would personally use the REST API. I have not done this or looked it to it but, seems to be the industry standard. https://github.com/datalek/silhouette-rest-seed
Giovanni Azua
@bravegag
Hi all, has anyone tried lately to deploy the play-silhouette-seed in Heroku?
I get close but my application starts to blow all kind of IoC errors
Christian Kaps
@akkie
I know that the play-silhouette-seed repo fails to deploy to heroku. But I have not looked into it. So I cannot say if it's IoC related.
Will look into it this afternoon
Giovanni Azua
@bravegag
Hi Christian! Thanks much appreciated!
Christian Kaps
@akkie
@bravegag Heroku works for me. I've fixed an issue with an old Heroku config. But now the seed template deploys as expected. No IoC issues
Giovanni Azua
@bravegag
@akkie, where do you have the successful setup? in play-silhouette-seed?
thanks in advance!
Christian Kaps
@akkie
@bravegag yes
Giovanni Azua
@bravegag
@akkie Hi Christian, good morning! I don't see the Heroku config changed in seed master, did you do it there? all I see is an upgrade of the SBT ...
gobandoGH
@gobandoGH
Hi @bravegag, I have a play-silhouette-seed based app (V 6.1) deployed in Heroku. No issues. How could I help ?
Christian Kaps
@akkie
@bravegag the failed deployment was due a config error in Heroku itself.
A wrong var that has worked with an old buildpack but not with a newer version
gobandoGH
@gobandoGH
@akkie , @AlbaroPereyra Thank you for your response
Yes, I intend to keep the App Rest API based.
I have learnt from Auth0 that Cookie Authenticator might be a bit of a trouble because of its stateful condition. Silhouette documentation discourage Cookie Authenticator for mobile as well. As I want to keep the App working for web and mobile, I am thinking of having separate endpoints for authentication, one based on Cookies and other other perhaps on JWT. Share model functionality decoupled form authentication.
Does this approach make sense to you ?
Giovanni Azua
@bravegag
@akkie @gobandoGH could you please share details on your Heroku configuration I could use as reference to pinpoint what’s going south with my deployment? That’d be extremely helpful ...
I have done step by step two times with the Playframework & Heroku Dev guides to deploy the app and everything looks ok but still all the IOC breaks and there is no other output
Giovanni Azua
@bravegag
Can you please send me screenshots of your Heroku settings? to bravegag@gmail.com of course concealing any private/security/confidential data
gobandoGH
@gobandoGH
@bravegag I have send you Heroku related deployment files to your email. Please let me know if further details are needed
Giovanni Azua
@bravegag
@gobandoGH I'm double checking everything .. thank you!
@akkie @gobandoGH this is the log I am getting from Heroku https://www.dropbox.com/s/34k1lp36bxjq6xi/heroku.log?dl=0
Christian Kaps
@akkie
@bravegag I think your config will not be loaded correctly. The config contains the module bindings and therefore Guice cannot load it
Have you set the PLAY_CONF_FILE var to application.prod.conf?
Giovanni Azua
@bravegag
yep
@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
Christian Kaps
@akkie
web: target/universal/stage/bin/play-silhouette-seed -Dhttp.port=${PORT} -Dconfig.resource=${PLAY_CONF_FILE}
-Dconfig.resource
not Dconfig.file
Giovanni Azua
@bravegag
Yep just caught the same :) I am running again :)
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