以下链接表示您可以将CookieAuthenticator用作无状态或有状态.
http://silhouette.mohiva.com/docs/authenticator
但我看不到任何选项可以在下面的链接做出选择.
http://silhouette.mohiva.com/v3.0/docs/config-authenticators#cookieauthenticator
我已经复制了以下示例的实现.这是无国籍还是有状态的?如果有状态我如何实现无状态身份验证?
用于在Ubuntu服务器上从git安装node.js和应用程序的完整命令堆栈(在Amazon EC2 上为Ubuntu 12.04)
我刚刚开始使用Java Play Framework,并向前迈出了一些步骤,但是现在我打算添加JavaEbean OEM,并仔细阅读了文档,但仍然收到错误NoClassDefFoundError:play / Configuration
application.conf
# This is the main configuration file for the application.
# https://www.playframework.com/documentation/latest/ConfigFile
ebean.default = ["models.*"]
Run Code Online (Sandbox Code Playgroud)
plugins.sbt
addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.7.0")
addSbtPlugin("com.typesafe.sbt" % "sbt-play-ebean" % "4.1.0")
Run Code Online (Sandbox Code Playgroud)
我的模特:
import io.ebean.Model;
public class Book extends Model {..}
Run Code Online (Sandbox Code Playgroud)
build.sbt
name := """BookStoreApp"""
organization := "com.example"
version := "1.0-SNAPSHOT"
lazy val root = (project in file(".")).enablePlugins(PlayJava, PlayEbean)
scalaVersion := "2.12.8"
libraryDependencies += guice
Run Code Online (Sandbox Code Playgroud)
我从sbt开始,进行了更新,一切都很好,但是如果我编译了,我会收到以下错误:
[error] java.lang.NoClassDefFoundError: play/Configuration
[error] at play.db.ebean.ModelsConfigLoader.apply(ModelsConfigLoader.java:27)
[error] at play.db.ebean.ModelsConfigLoader.apply(ModelsConfigLoader.java:21)
[error] at play.ebean.sbt.PlayEbean$.$anonfun$configuredEbeanModels$4(PlayEbean.scala:153) …
Run Code Online (Sandbox Code Playgroud) 我Content-Security-Policy:default-src 'self'
在网页上使用标题.
当我使用启用的"Grammarly"chrome扩展程序加载此页面时,Chome在控制台中抛出错误:
Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAIt0ABEAAAABQDwAAQABAAAAAAAAAAAAAAAAAAAAA…CwKGBmIIpVWLACJWGwAUVjI2KwAiNEswkKAwIrswsQAwIrsxEWAwIrWbIEKAZFUkSzCxAEAisA' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.
Run Code Online (Sandbox Code Playgroud)
我认为它也可能与其他插件一起发生.
你用什么策略?
在控制台中查看包含错误的页面是一种糟糕的体验.用户不会关心这是实际页面问题还是他们"喜欢扩展".
正如我所见,这个标题并没有被广泛使用.
google-chrome google-chrome-extension content-security-policy