by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 04 11:09

    akkie on gh-pages

    updated site (compare)

  • May 04 10:58

    akkie on gh-pages

    updated site (compare)

  • May 04 10:56

    akkie on gh-pages

    updated site (compare)

  • May 04 10:45

    akkie on master

    Fixed Auth0ProfileParser to get… (compare)

  • May 04 10:45
    akkie closed #578
  • May 04 10:44
    akkie commented #578
  • May 03 03:23
    coveralls commented #578
  • May 03 03:02
    ymotchi opened #578
  • 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)

Aidar
@SunPj
@neimspace11 Is there any other output?
@neimspace11 Do you have both frontent and backend parts running?
neimspace11
@neimspace11
Yes, both front-end and back-end parts are running.
1) Back-end part through sbt run and front-end part through npm run serve. Both parts are shown in terminal that they are running successfully
2) If I open localhost:8080, then no error is being received and landing page is being opened.
3) If I open localhost:9000, then I receive 500 Internal server error in browser and that error log for back-end part which i pasted before.
Aidar
@SunPj
@neimspace11 Could you try following
Create devEnv.conf file in <project_root>/conf directory and specify there your keys
play.filters.headers.contentSecurityPolicy = "*"

silhouette {
  csrfStateItemHandler.signer.key="..."
  oauth1TokenSecretProvider.signer.key="..."
  oauth1TokenSecretProvider.crypter.key="..."
  authenticator.sharedSecret="..."
}

sendgrid.api.key = "..."


play.crypto.secret="..."
neimspace11
@neimspace11
Okey, I will try that. Will let you know if it helped.
Aidar
@SunPj
Could you double check your conf files and all changes and make sure there is no any non utf8 symbols. That error says that the issue relates to parsing but I am not sure
neimspace11
@neimspace11
conf files indeed was the cause of that issue, so now that's solved
Aidar
@SunPj
@neimspace11 What was the cause of the issue? Was it non UTF8 symbol? Does everything work well now?
neimspace11
@neimspace11
@SunPj I removed all ENV parameters (no need for my local deployment) and it started to work. Now localhost:9000 opens fine and I can connect to PostgreSQL database.
Btw, was wondering if you have any plans to finish your todo list:
  • Integration Silholuette's social auth
  • Test heroku autodeployment
  • User management page for admin
Aidar
@SunPj
@neimspace11 I am working on them. Hope will finish User management page for admin by the end of this week
neimspace11
@neimspace11
Great! Keep up the good work !
Aidar
@SunPj
@neimspace11 User management functionality is already in place
Andrey Zhukov
@zulus23
Hello! I'm begginer in Silhouette. I have error: A binding to com.mohiva.play.silhouette.api.actions.SecuredErrorHandler was already configured at modules.SilhouetteModule.configure(SilhouetteModule.scala:41) and I don't know what's a problem, setup module is bind[UnsecuredErrorHandler].to[CustomUnsecuredErrorHandler]
bind[SecuredErrorHandler].to[CustomSecuredErrorHandler]
Aidar
@SunPj
@zulus23 Seems you are trying to define Guice binding for component that has already defined in Silhouette module. Just remove your one and error should go away
Andrey Zhukov
@zulus23
thanks. I protected index with silhouette.SecuredAction and in SecurityAction.scala I find class class SecuredErrorHandlerModule extends Module {
def bindings(environment: PlayEnv, configuration: Configuration) = {
Seq(
bind[SecuredErrorHandler].to[DefaultSecuredErrorHandler]
)
}
} and I think it's code don't give bind my SecuredErrorHandler.
Andrey Zhukov
@zulus23
Sorry. I found my error. I should add in application.config this rows disabled += "com.mohiva.play.silhouette.api.actions.SecuredErrorHandlerModule"
disabled += "com.mohiva.play.silhouette.api.actions.UnsecuredErrorHandlerModule"
neimspace11
@neimspace11
@SunPj Thanks!
Aidar
@SunPj
@neimspace11 I am going to integrate social login by the end of this week
neimspace11
@neimspace11
@SunPj Sounds perfect!

Btw, was testing the app locally and encountered following problem when trying to 'Sign In' with the user which is activated:

POST http://localhost:9000/signIn 500 (Internal Server Error)

On back-end receiving following error:

Caused by: com.mohiva.play.silhouette.api.exceptions.AuthenticatorInitializationException: [Silhouette][jwt-authenticator] Could not init authenticator: JWTAuthenticator(6434c722ab87ceb8c5b514e5d9659f47c2deb68cbd021786a1a8564ce3e4c7eb5116002584c7187fb81803dcae53eb0c453fdecccb4b87821eb6848d96bcd7a481504f4b5f1b1eb76abbea1915dc66570759f52caac81b5c0407777622f7408787fd5804a9c2e1f1516646bced070d3c806ccd001abbb52d07dee2f3b7f53162,LoginInfo(credentials,test@test.lv),2019-12-10T14:28:37.659+02:00,2019-12-11T02:28:37.659+02:00,None,None)

Any ideas, what could be wrong ?

Aidar
@SunPj
@neimspace11 Don't you use some existing database (used for another app) for new app with different secret keys?
neimspace11
@neimspace11
Hmm, nope. I have created a separate DB for this app. On DB level I can see that password is stored and user is activated, but when trying to log-in I am receiving this error.
Aidar
@SunPj
@neimspace11 Is there any additional info in your stack? Don't you have something like Caused by: com.nimbusds.jose.KeyLengthException: The secret length must be at least 256 bits?
neimspace11
@neimspace11

Ohh, yes. There is such:

Caused by: com.atlassian.jwt.exception.JwtMalformedSharedSecretException: Failed to create MAC signer with the provided secret key
Caused by: com.nimbusds.jose.KeyLengthException: The secret length must be at least 256 bits

Aidar
@SunPj
@neimspace11 That means that your secret keys are not big enough (append some more characters, I mostly use play secret generator, that's safer, better and easier)
neimspace11
@neimspace11
Thanks for the hint. Will try !
Aidar
@SunPj
@neimspace11 See Generating an application secret chapter here https://www.playframework.com/documentation/2.7.x/ApplicationSecret
neimspace11
@neimspace11
@SunPj unfortunately, this does not helped. Same error.
I have tried to set play.http.secret.key="long_randomly_generated_secret" in application.conf and also in devEnv.conf, but neither way it helped. Weird.
Aidar
@SunPj
@neimspace11 Check all your secret keys not just play's one. Look at github page of the project and make sure all keys have proper length
neimspace11
@neimspace11
@SunPj I double-checked all the secret keys (was missing some), and now it finally worked. So all good. Thanks for the help.
Aidar
@SunPj
@neimspace11 Happy to hear that!
neimspace11
@neimspace11

@SunPj Btw, one thing what could be useful to add in your TO DO items - implement an error message if users tries to 'Sign Up' with the e-mail what is already registered. Currently, there is no message on UI side (and no logs on back-end side). In browser it silently receives:

POST http://localhost:9000/signUp 409 (Conflict)

Aidar
@SunPj
@neimspace11 Oh. I remember that. I will fix that during next days. Thanks for feedback
@neimspace11 I have just pushed changes with loading indicator on sending the signin/signup forms so they look nicer
neimspace11
@neimspace11
@SunPj Great job!
Aidar
@SunPj

implement an error message if users tries to 'Sign Up' with the e-mail what is already registered

@neimspace11 I have solved that. Changes are in github and in demo heroku app

neimspace11
@neimspace11
@SunPj Great! This was fast.
nafg
@nafg
Hi, can I expect support for Play 2.8.0 any time soon?
nafg
@nafg
@akkie are you around now?
nafg
@nafg
@akkie are you around?
Christian Kaps
@akkie
@nafg I'm here
nafg
@nafg
@akkie have you considered setting up Scala Steward?
Christian Kaps
@akkie
@nafg Yes, sure. But the main focus for me was getting the framework agnostic version of Silhouette to an end.
Aidar
@SunPj
@neimspace11 I have done Silhouette social authentication integration. https://github.com/SunPj/silhouette-vuejs-app
Although authentication via OAuth1/2 leads to new user to be created. I will work on merging users functionality so it won't be allowed to signUp via social if there is existing user with eq email. I will add buttons to link social accounts to user profile, instead
neimspace11
@neimspace11
@SunPj Thanks a lot!
Tudor Anastasiu
@skypper
Hi, I would like to create and ActionFilter that takes SecuredRequest as input and filters based on requrest.identity. However there is a compiler error because ActionRefiner takes requests that depend on a single type parameter, the body, whereas SecuredRequest depends on 2 type parameters (the env and body). Any advice?
case class SecuredRequest[E <: Env, B]
trait ActionFilter[R[_]]
Aidar
@SunPj
@neimspace11 Hi. I have added Recaptcha support. Just if you are interested.