Silhouette is an authentication library for Play Framework applications that supports several authentication methods, including OAuth1, OAuth2, OpenID, Credentials or custom authentication schemes.
Please review and any feedback or comments are most welcome.
Hi all, does anybody have an example of using a UserAwareAction with a file upload in a form submission - I'm trying to allow a user to submit a form with an image in it. effectively I want to do this
silhouette.UserAwareAction.async(parse.multipartFormData) but the types and I'm not sure how to square the circle.
@rorygraves I was about to post you what I did to handle PDF and image uploads. But looks like you already have a solution. One note though, depending on the uploaded file size you may need to adjust the buffer of the parser. It is in our application.conf
play.http.parser.maxMemoryBuffer = 512k for example.
It depends to what degree you require data isolation for each tenant. Silhouette ootb stores all the user records, credentials (password and oauth tokens, etc) in multiple tables of one database. But it’s hard to be more specific without more details on what you are trying to achieve.
did anyone encountered that?
Hi Also switched from mohiva 5.0.0 - 5.0.7 and play 2.7 then I get the following exception
play.api.UnexpectedException: Unexpected exception[AbstractMethodError: Method com/mohiva/play/silhouette/api/actions/DefaultSecuredErrorHandler.play$api$mvc$Results$_setter_$PreconditionRequired_$eq(Lplay/api/mvc/Results$Status;)V is abstract]
at play.core.server.DevServerStart$$anon$1.reload(DevServerStart.scala:200)
at play.core.server.DevServerStart$$anon$1.get(DevServerStart.scala:127)
at play.core.server.ssl.ServerSSLEngine$.createSSLEngineProvider(ServerSSLEngine.scala:30)
at play.core.server.AkkaHttpServer$$anon$2$$anon$3.sslEngineProvider$lzycompute(AkkaHttpServer.scala:469)
at play.core.server.AkkaHttpServer$$anon$2$$anon$3.sslEngineProvider(AkkaHttpServer.scala:469)
at play.core.server.AkkaHttpServer$$anon$2$$anon$3.engineCreateSSLEngine(AkkaHttpServer.scala:470)
at javax.net.ssl.SSLContext.createSSLEngine(SSLContext.java:329)
at akka.stream.scaladsl.TLS$.$anonfun$apply$2(TLS.scala:88)
at akka.stream.impl.io.TLSActor.liftedTree1$1(TLSActor.scala:157)
at akka.stream.impl.io.TLSActor.<init>(TLSActor.scala:157)
Caused by: java.lang.AbstractMethodError: Method com/mohiva/play/silhouette/api/actions/DefaultSecuredErrorHandler.play$api$mvc$Results$_setter_$PreconditionRequired_$eq(Lplay/api/mvc/Results$Status;)V is abstract
at com.mohiva.play.silhouette.api.actions.DefaultSecuredErrorHandler.play$api$mvc$Results$_setter_$PreconditionRequired_$eq(SecuredAction.scala)
at play.api.mvc.Results.$init$(Results.scala:669)
at com.mohiva.play.silhouette.api.actions.DefaultSecuredErrorHandler.<init>(SecuredAction.scala:299)
at GatewayChamberLoader$$anon$1.securedErrorHandler$lzycompute(GatewayChamberLoader.scala:144)
at GatewayChamberLoader$$anon$1.securedErrorHandler(GatewayChamberLoader.scala:144)
at GatewayChamberLoader$$anon$1.securedRequestHandler$lzycompute(GatewayChamberLoader.scala:147)
at GatewayChamberLoader$$anon$1.securedRequestHandler(GatewayChamberLoader.scala:147)
at GatewayChamberLoader$$anon$1.securedAction$lzycompute(GatewayChamberLoader.scala:151)
at GatewayChamberLoader$$anon$1.securedAction(GatewayChamberLoader.scala:151)
at GatewayChamberLoader$$anon$1.silhouetteDefaultEnv$lzycompute(GatewayChamberLoader.scala:169)Any help would be appreciated
Version 5 istn't compatible with Play 2.7. Please see mohiva/play-silhouette#553 and mohiva/play-silhouette#551
If you have an idea why the build for mohiva/play-silhouette#553 failed, then any help is appreciated
@irhspur This example uses an old version of Silhouette and it's based on Angular. But the concepts are still the same
A relative actual Silhouette/React app without social login can be found here: https://github.com/setusoft/silhouette-play-react-seed
Is there a good way to decode the state when the user denies access? I have a lot of useful information in the state that I need access to. Currently, I get an exception and it doesn’t seem to have the state information in there. I can see that the request sent back from the OAuth provider has the state variable.
It would’ve been really nice if the state extraction was separate from the handling of the received code or status. Looking thru the code, looks like it’s a protected resource.
It would’ve been really nice if the state extraction was separate from the handling of the received code or status. Looking thru the code, looks like it’s a protected resource.
When a user authenticates with an OAuth provider and decides in the flow to decline, the provider will call me with access denied. This shows up as AccessDenied exception. I need to get at the state so I can figure out a decent way of handling the error - like redirecting someplace.
Hey there @akkie Big thanks for making Silhouette available to the world! I'm working on a project and one of the things I can't figure out is whether I can use the auth data obtained by silhouette to call Google APIs after the user has logged into google using Silhouette. I can't seem to find a way to do that but it seems like a common case. Am I looking in the wrong place? As an example, if one wanted to fetch detailed information about the logged in user one might use something similar to this: https://developers.google.com/admin-sdk/directory/v1/quickstart/java But that would trigger another auth flow, which seems silly.
Hi everyone, I'm looking at moving to Silhouette from PA. I have over time built a seed for apps but since PA is Java native and I need Scala then the result is a bit hacky (e.g. creating JavaContext for Scala). Anyway, what's the closest (and latest Play 2.7) Silhouette seed to what I have https://github.com/bravegag/play-authenticate-usage-scala including: username/password authentication with email integration, social authentication, Slick backend and DAO with Postgres DB, Google recaptcha TOTP, Remember Me using cookies or otherwise. TIA!
How do you implement sudo Actions in Silhouette? by sudo I mean when we need to re-auth the user because of trying to access sensitive information such as billing or security settings. Sudo activates when the user logged in using a cookie and then attempts to access (view or edit) sensitive information.
@bravegag I'll post the link to the forum post, so that others can follow the discussion. http://discourse.silhouette.rocks/t/how-do-you-solve-in-silouette-the-sudo-actions-use-case/340/4
I can overwrite the defaultSecuredErrorHandler in every Action, but I was wondering if there was another way
@pektinasen The silhouette stack can be bound per environment and so the global error handler can also be bound per environment. https://github.com/mohiva/play-silhouette/blob/master/silhouette/app/com/mohiva/play/silhouette/api/Silhouette.scala#L30
