More security! In a modern application the authentication on its own is not sufficient. It’s a common practice to grant different privileges to a group of users. Also when we talk about users, the two basic uses cases come to our mind - user log-in and log-out. In this post we will cover user authorization and OAuth 2 token revocation in the Spring Boot 2 framework. This tutorial is a second part of the recent post introducing token-based authentication in the Spring framework.
Yet another tutorial? Some time ago I’ve been asked to setup authentication for a Spring Boot-based REST application. “Easy-peasy” I said to myself. I’ve been coding in Java for many years. I’ve been using Spring framework since the very early version when you had to love the XML. I took into account all the requirements and proposed a solution with OAuth 2 as an authentication framework. I was happy to start a development.
The Problem I recently updated my RxJava dependency from version 1.x to 2.x. Everything looks very good in RxJava world - new version seems to be more coherent and consistent. Much cleaner. You can find large amount of details in an official RxJava Github Repo. First sentences on this page say that: RxJava 2.0 has been completely rewritten from scratch on top of the Reactive-Streams specification. The specification itself has evolved out of RxJava 1.
Introduction Recently I had an undoubted pleasure to work with SOAP based web services. The client I was using was JAX-WS compliant and generated using wsimport tool. In theory for modern systems they are basically thing of the past but in reality they are still present. Let’s say that your nice and clean Java code uses RxJava and tries to be reactive and asynchronous. In that case you really want to call SOAP web service as you would any other Rx Observable/Completable source.