Spring Security OAuth2
This guide describes the integration of Spring security’s OAuth2 client. Authentication is done via OAuth2 and authorization via Shiro.
Dependency Management
If your application inherits from the Apache Causeway starter app (org.apache.causeway.app:causeway-app-starter-parent
) then that will define the version automatically:
<parent>
<groupId>org.apache.causeway.app</groupId>
<artifactId>causeway-app-starter-parent</artifactId>
<version>2.0.0-RC1</version>
<relativePath/>
</parent>
Alternatively, import the core BOM. This is usually done in the top-level parent pom of your application:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.causeway.core</groupId>
<artifactId>causeway-core</artifactId>
<version>2.0.0-RC1</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
Dependency
In the webapp module of your application, add the following dependency:
<dependencies>
<dependency>
<groupId>org.apache.causeway.extensions</groupId>
<artifactId>causeway-extensions-spring-security-oauth2</artifactId>
</dependency>
</dependencies>
Update AppManifest
In your application’s AppManifest
(top-level Spring @Configuration
used to bootstrap the app), import CausewayModuleSecuritySpring
and CausewayModuleExtSpringSecurityOAuth2
modules.
Neither of these modules provide an implementation of the Authorizor SPI, so we must also configure one.
For the purpose of this walkthrough, we’ll use the implementation provided by Shiro, namely AuthorizorShiro
.
@Configuration
@Import({
...
CausewayModuleExtSpringSecurityOAuth2.class, (1)
AuthorizorShiro.class,
...
})
public class AppManifest {
}
1 | The CausewayModuleExtSpringSecurityOAuth2 module brings in a transitive dependency on CausewayModuleSecuritySpring .
Make sure though that no other |
It is also possible to use with other Authorizor
implementations; for example, using SecMan.
Design
The module brings in a transitive dependency to org.springframework.boot:spring-boot-starter-oauth2-client
.
Using this, it provides an implementation of the AuthenticatorConverter SPI that recognises the OAuth2
principal provided by the Spring OAuth2 client.
Walk-through
Using Spring Security we can configure your app with various authentication providers. In this section we describe how to modify the HelloWorld starter app to use github as an OAuth2 provider. The steps here are based on this Spring tutorial.
Code Changes
The OAuth2 integration provided by Spring (seemingly) forwards onto an "/login" endpoint immediately after the user has logged into github, but with an authenticated principal. We therefore use a controller to simply forward directly onto the Wicket Viewer:
-
create this page to redirect:
templates/redirect-immediately.html<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html xmlns:th="http://www.thymeleaf.org"> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="refresh" content="0;url=/wicket/" /> </head> <body> <div id="wrapper"> </div> </body> </html>
-
define this controller for
/login
:LoginController.java@Controller @RequestMapping({"/login"}) public class LoginController { @RequestMapping( produces = {"text/html"} ) public String login(HttpServletRequest request, HttpServletResponse response) { return "redirect-immediately"; } }
Next, add in LoginController
to the AppManifest
.
public class AppManifest {
}
@Configuration
@Import({
...
CausewayModuleExtSpringSecurityOAuth2.class,
AuthorizorShiro.class,
LoginController.class,
...
})
public class AppManifest {
}
Next configure authenticationStrategy and permissionResolver for realms, and add the userId:
[main]
authenticationStrategy=org.apache.causeway.extensions.secman.delegated.shiro.realm.AuthenticationStrategyForSecMan
securityManager.authenticator.authenticationStrategy = $authenticationStrategy
securityManager.realms = $iniRealm
permissionResolver = org.apache.causeway.security.shiro.authorization.CausewayPermissionResolver
iniRealm.permissionResolver = $permissionResolver
...
[users]
...
your.id = ,admin_role
...
Lastly (and optionally), the swagger/REST API is not configured for oauth2, so we replace the index.html
page with one to redirect straight to the Wicket Viewer:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html xmlns:th="http://www.thymeleaf.org">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="refresh" content="0;url=/wicket/" />
</head>
<body>
<div id="wrapper">
<!-- we just redirect immediately, because swagger/restful API not configured to use spring security -->
</div>
</body>
</html>
Configuration
We are now ready to configure the app. As described in the this Spring tutorial:
-
register the app on github:
-
obtain the clientId and create a new client secret:
-
update the configuration:
config/application-github-example.propertiesspring.security.oauth2.client.registration.github.clientId=XXXX spring.security.oauth2.client.registration.github.clientSecret=XXXXXXXX
Run the application
You should now be able to run the application, setting the "github-example" profile using this JVM argument:
-Dspring.profiles.active=github-example
If you are already signed into github:

then you should be logged in directly; the app will show your user name:

On the other hand, if you are not signed in then you will be redirected to the github login page:

If you have 2FA enabled, then this also works:

and then, once again, you will be redirected to the app and it will show your user name:

Finally, if you log out then Spring will show a page to allow you to trigger the login process:
