You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hence the conf object is almost empty now, meaning that almost all settings are now defined and documented in reference.conf, and loaded through pureconfig into the super-config-case-class.
ToDo
Use Silhouette's Credentials type for, well, credentials
Use Silhouette's IdentityService to resolve user names to accounts
Use Silhouette's CredentialsProvider together with AuthInfoRepository to authenticate users.
Check "As part of this change passwords are now hashed with bcrypt when they are added to the authentication info repo in AuthModule. Silhouette makes this trivial, and it slows down authentication, making brute-force attacks against passwords less feasible."
Problem
play2-auth seems less actively maintained and doesn't support Play 2.6 yet, see t2v/play2-auth#184.
I propose to switch to Silhouette. I think it's
Play 2.6 support implies Scala 2.12 support; without play 2.6 we'll not be able to use Scala 2.12
Code
Breaking changes
Moved all auth configuration into a case class, affecting the following keys:
broccoli.auth.session.allowMultiLogin
→broccoli.auth.session.allow-multi-login
broccoli.auth.allowedFailedLogins
→broccoli.auth.allowed-failed-logins
broccol.auth.conf.accounts[].instanceRegex
→broccol.auth.conf.accounts[].instance-regex
Hence the
conf
object is almost empty now, meaning that almost all settings are now defined and documented inreference.conf
, and loaded through pureconfig into the super-config-case-class.ToDo
Credentials
type for, well, credentialsIdentityService
to resolve user names to accountsCredentialsProvider
together withAuthInfoRepository
to authenticate users.SilhouetteProvider
inAuthModule
, then haveSilhouette
injected into controllers that authenticate and use it for authenticationReferences
User Aware Handler
Secure Websocket
The text was updated successfully, but these errors were encountered: