The goal of the post is to share an idea how can we provide the basic authentication and OAuth 2 authentication for the APIs, meaning with new technologies we need to support the OAuth2 for new clients, but at the same time we still need to support the basic authentication way of securing the APIs maybe for time for existing API Users.
In general, in basic auth clients call API keeping
username:password in the Authorization header for the APIs. By standard basic auth annotation, the
username:password will be Base 64 encoded string.
Now for the new clients, you would want to keep the API the same and change the authorization part of the API, maybe the OAuth2 token in the authorization header instead of the basic auth header, something like.
With this you want your Spring Java Rest APIs to have support both authentication, depending on the client header type let the application decide the route to take for authentication.
For this to work, we will have to understand the Spring security a bit. In the Spring security, you will find the filter chain the gets executed upon any request from the client, which could be requested from web browsers, mobile clients, or Rest clients.
For the request handling, we need to configure the WebSecurityConfigureAdapter in the Spring configuration, like
The above code tells the Spring that any request for book APIs should be authenticated, internally it’s going to check for SecurityContext information when serving these requests.
Now, for Spring basic authentication we generally configure the daoAuthentication provider with an overridden method. So whenever the spring security chain executed the Springs basic auth filter will be called and internally it calls the dao provider for authentication. It’s a lengthy topic to cover in one post, I will cover that up in a separate post. but, bottom line is that you need to have the dao provider along with the basic authentication filter.
So for our example we have bookDaoAuthenticationProvider, with HTTP basic on it. All basic auth requests will be served from Spring’s BasicAuthenticationFilter if they have the Basic keyword starts in the Authorization header, that’s Spring’s internal logic.
For OAuth2 requests, we can use the AbstractPreAuthenticatedProcessingFilter, as the tokens would be pre-validated by the OAuth2 token servers and it’s just needed the verification from the Spring application now. Tokens are generally JWT tokens.
We can configure the security to handle requests like
The booksJwtPreAuthFilter can be configured like —
Keep in mind the API request Authorization header is important here. If it has a Basic keyword it would be served by BasicAuthFilter in the chain and SecurityContext would be created. Now AbstractPreAuthenticatedProcessingFilter filters would be only invoked if the security context has not been created yet, that’s the whole point of this logic.
Hope this gives a good idea about the Spring Rest API authentication for Basic Auth and For OAuth2 for that matter any other security protocol as well.
This content was originally published here.