magnolia-k on main
avoid `reflectiveCalls` (#1400) (compare)
magnolia-k on main
update to jetty 11 (#1399) (compare)
magnolia-k on main
Update metrics-servlet, metrics… (compare)
magnolia-k on main
Update junit-4-13 to 3.2.13.0 (… (compare)
magnolia-k on main
Update scalatest-featurespec, .… (compare)
magnolia-k on main
Update scala-collection-compat … (compare)
magnolia-k on main
Upgrade to Jetty 10 / Servlet A… (compare)
I can ignore it, becuase the code compiles and the tests run fine but intelliJ will prompt me, that there is an issue in the code everytime I commit changes ...
Perhaps an issue with the IntelliJ scala Plugin.
Sorry. Last update for today. I am a bit confused.
I use the dependencies like the following now:
libraryDependencies ++= Seq(
"org.scalatra" %% "scalatra" % "2.7.0",
"org.scalatra" %% "scalatra-scalatest" % "2.6.0" % "test",
"org.scalatra" %% "scalatra-json" % "2.7.0",
"org.json4s" %% "json4s-jackson" % "3.5.2",
"ch.qos.logback" % "logback-classic" % "1.2.5" % "runtime",
"org.eclipse.jetty" % "jetty-webapp" % "9.4.43.v20210629" % "container",
"javax.servlet" % "javax.servlet-api" % "3.1.0" % "provided",
)
Now I have no more problems reported by intelliJ. Hope this helps someone to get you scalatra app running without intelliJ issues ;-)
filter
with an after
method should do it right? In the after
you can set the HSTS header to the response.
Hello together. I have a question regarding scalatra and SSO.
What I want to do
When someone fetches data from my scalatra backend, he has to be authenticated. As authentication mechanism I have to use SAML SSO with Azure as IdP.
So, when someone is not authenticated, he has to enter his credentials at the IdPs page and will be redirected to the requested data endpoint.
In addition to that, an authenticated user must have roles, which do not come from the IdP. So I want each new user persisted in the database with a default role and then assign roles to them later.
What I currently have
I use pac4j for the SAML SSO login, which works just fine. For the session handling I use buji-pac4j (Apache Shiro Integration) which receives the Profile Data from Pac4J and puts in into the session store.
But for me it's now unclear how to handle the roles of the users. Can I somehow persist the profiles to a database and read them from there again, when permissions have to be checked?
Is there any example project out there, where I can see how this can be done?
Thanks for your help!
Hi guys! I have some warnings during development.
To reproduce:
sbt new scalatra/scalatra.g8
and all defaults;JettyLauncher.scala
as described in Standalone deployment + adjust build.sbt.Now when I run in sbt ~Jetty/start
console logs ≈ 1100 lines of warnings with similar content as:
WARN:oeja.AnnotationParser:qtp1427810650-12: javax.servlet.AsyncEvent scanned from multiple locations: jar:file:///Users/emris/scala/sanga/target/webapp/WEB-INF/lib/javax.servlet-api-3.1.0.jar!/javax/servlet/AsyncEvent.class, jar:file:///Users/emris/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/eclipse/jetty/jetty-runner/9.4.29.v20200521/jetty-runner-9.4.29.v20200521.jar!/javax/servlet/AsyncEvent.class
Do I miss some configuration option to fix these conflicts?
@ApiModel
from scalatra doesn't have the same fields as the one from io.swagger
so i can't find a way to get this to work