Enjoy the ride!
Enjoy the ride!
- [TYNAMO-231] - Integrate Swagger
- [TYNAMO-235] - Make it super easy to add CORS support.
+ issues on the github milestone 0.4.0.
For release notes, I'm thinking in the future I'm just going to link to the Github milestone for the release. Let's practice: tapestry-routing 0.1.0 milestone.
Release Notes - tapestry-security-0.6.0
* [TYNAMO-147] - Make tapestry-security compatible with tapestry-5.4
* [TYNAMO-236] - Migrate tapestry-security to tapestry 5.4 beta
** Github issue
#1: Implement a new default CookieRememberMeManager for creating smaller rememberme cookies (how do you get "release notes" out from Github?)
Now that a public beta of Tapestry 5.4 is out, we are also starting a module upgrade and release cycle for 5.4 compatibility. Tapestry-security 0.6.0 is first in line, watch for the release announcement later!
Project Lambda was merged to the mainline a while back but b106 is the official developer preview release and (depending on how you look at things) it was actually released on schedule. My main interest beyond lamba expessions is how the JRE performs with the new metaspace. Naturally Mark has a few forewords to say about the new JDK8 build, go get yours!
- [TYNAMO-211] - Allow parametrized configuration in federated login components for setting rememberMe in the token
- [TYNAMO-220] - Implement rolling tokens support for federated accounts
- [TYNAMO-181] - Implement DefaultJpaFederatedAccountServiceImpl
- [TYNAMO-182] - Support GitHub federated login
- [TYNAMO-93] - Support for Google OAuth 2.0
- [TYNAMO-217] - returnPageName is required since there's no defaultReturnPage prop in AbstractOauthSignIn
This two little but useful libraries have new versions available.
- tapestry-resteasy 0.3.2 is mostly a maintenance release for updating the JAX-RS dependency to JBoss' resteasy 3.0.1.Final.
- tapestry-routing 0.0.6 introduces:
- cleaner and more flexible API design.
- support for reloading of @At annotations (TYNAMO-8814)
- support for the tapestry.application-folder symbol (TYNAMO-15717)
- the ability to contribute Routes from different sources
- a new annotation called @Route as an alternative to the @At annotation
The Tynamo Team.
- [TYNAMO-176] - Incorrect redirect to login page in case of ajax request
- [TYNAMO-125] - Else block for the security components
- [TYNAMO-193] - Allow temporarily disabling security for an invocation of Callable
- [TYNAMO-195] - Make LoginForm error messages localizable
- [TYNAMO-183] - Improve support for Instance-Level Access Control
Yes, we just might have forgotten to announce "a few" releases we've made. We got busy, what can you say? Besides our marketing dudes never do anything anyway. Let's start the year with a bang and correct the situation right now (after taking the marketing department behind the shed). Here's a recap of the previously unannounced releases we've made in the last four months:
We finally implemented a built-in full text search. The Hibernate version is using HibernateSearch because it's ah so automatic and nice. Only thing is that it's local only. For the JPA version, we fully integrated ElasticSearch, the best thing since full-text bread. I dare say our integration is better than the one that Play framework has to offer. It seamlessly integrates with SQL-based search and is easy to extend. tapestry-model continues to be better suited only for the more experienced Tapestry users. One day we'll write proper documentation for it and surprise you all.
A fix for TYNAMO-183 forced our hand because of some dependencies on 5.3 so we decided to push out 0.5.0 a bit early. We'll get the rest of the improvements in later. We are also dropping support for T5.0/5.1 but hey it's open source. If you find a bug in the earlier releases, send it to us and we'll patch it.
TYNAMO-129, or rememberMe with rollingtokens made it as a new submodule of federatedaccounts. There's just no reason to use those puny, insecure and ordinary remember me cookies anymore. More at my blog post on RememberMe with rolling tokens.
First, the younger JPA version of the well battle-tested seedentity library pulled next to the hibernate-seedentity, turned her head and waved, then sprinted ahead laughing, leaving the hibernate guy sobbing in dust (in terms of features).
I still think it's the coolest little library out there and just wouldn't be possible to implement without the lovely distributed configuration of Tapestry. You aren't still modifying your html text content in an offline text editor, are you? Now I just need to integrate conversation and inline image support.
Want to secure your data instances? This one works so well it's annoying.
In the past five years, I worked on a number of greenfield projects. In three out of four, we ended up choosing Grails - it is very hard to deny the market & mindshare , the expansive documentation, the big name company behind the project, the large community, a massive number of plugins (for pretty much anything that you'd want), the end-to-end stack (so, you don't have to choose your ORM, DI, etc) and the ease of getting started with a Grails project.
However, after working on a couple of these Grails projects for a few years, the latest project I got involved with , I chose Tapestry. In some cases, I've missed some of the niceties that Grails brings out of the box, but without too much effort I've been able to replicate them fairly easily.
The biggest reasons for picking Tapestry over Grails on this latest project have been:
- The inability to aggressively refactor your code - the dynamic nature of the language is nice when you want to knock something out quickly, and saves you a few lines of code here and there. However, after the codebase gets to a certain size, the inability to reliably refactor the codebase made the codebase difficult to evolve. Sure, IntelliJ & NetBeans has some support for refactorings in Groovy; however, it is not even close to the level of depth and ease of what you get with Java. I love Groovy to death, have been using it for many years (since it was in jsr-1 version) but ... the tool support is just not there yet (and likely will never be) and for a team of developers Java just ends up being a better choice (at least in the context of my team)
On the first issue, if you will be using Groovy for your pages, you will be in the same boat as Grails. Personally, I wouldn't recommend it - Tapestry already pushes the envelope on Java quite a bit, so your Java code ends up being very short and sweet already. In the past, I had attempted to use Scala in a tapestry app, and ended up having to just deal w/ some of the mismatches between the language and the framework and my pages ended up looking up like the same old java pages I would have had but with a different syntax.
On the second issue, there is the grails resources plugin that tries to pull resources kinda like Tapestry, but using it requires this artificial separation into resource bundles which seems to be a PITA and somewhat mind bending.
On the abundance of Grails plugins - after using a bunch for the projects I was working on, it turned out that many were not well maintained so we hadto take over and maintain them ourselves. Sometimes, they're a good starting point, but in the end ended up less of a factor than I initially thought.
I originally very much enjoyed the Grails build system (running on top of Gradle); however, with a pretty simple project setup, Maven seems to bejust as straightforward. If you wanted Gradle, you could use that for your Tapestry app, and be on-par w/ Grails.
On the latest project that I chose Tapestry for , I have been very happy with my choice. On a few occasions I've run into some frustrations (e.g. for rendering emails, I ended up having to use Freemarker, whereas with Grails the template rendering for emails comes for 'free' ; I had to build my own equivalent of the Grails "console" plugin where you can run Groovy commands inside of your running application); however, in all cases, the solution has turned out to be more elegant than I had expected (albeit, it required deeper tweaks in the framework than I had expected).
Persistent login cookies are the cookies that are stored with your browser when you click the "remember me" button on the login form. I would like to be able to say that such cookies are obselete, and we have a better way of handling user logins, but they aren't, and we don't.
The following recipe for persistent cookies requires no crypto more powerful than a good random number generator.
- Cookies are vulnerable. Between common browser cookie-theft vulnerabilities and cross-site scripting attacks, we must accept that cookies are not safe
- Persistent login cookies are on their own sufficient authentication to access a website. They are the equivalent of both a valid username and password rolled into one
- Users reuse passwords. Hence, any login cookie from which you can recover the user's password holds significantly more potential for harm than one from which you can not
- Binding persistent cookies to a particular IP address makes them not particularly persistent in many common cases
- A user may wish to have persistent cookies on multiple web browsers on different machines simultaneously
With all this in mind, I've always implemented rememberMe based on rolling tokens in the various web applications I've worked on. However, I've never attempted to provide it as a reusable module until one day a few months ago while I was working on federatedaccounts it hit me: rolling tokens can be thought of as just another "remote" authentication provider that can be federated with the main account. For some months now, we've happily been using tynamo-federatedaccounts-rollingtokens in production. I added some quick documentation for it at the end of the generic tynamo-federatedaccounts guide, have (secure) fun with it!