Keycloak is based on a set of administrative UIs and a RESTful API. Keycloak supports fine-grained authorization policies and is able to combine different access control mechanisms such as:
Attribute-based access control (ABAC)
Role-based access control (RBAC)
User-based access control (UBAC)
Context-based access control (CBAC)
- Securing Spring Microservices with Keycloak part 1
- Securing Spring Microservices with Keycloak part 2
- REST Service Protected Using Keycloak Authorization Services
- The sources from above post
- Keycloak github quickstarts
- About policies and authorization
- [The Benefits of Migrating from ADFS to Keycloak](The Benefits of Migrating from ADFS to Okta)
Many enterprises today are looking to implement a single sign-on (SSO) so their users can easily access all of their cloud and web applications without authenticating to each application individually. They conclude that the solution for single sign-on from Active Directory is Active Directory Federation Services (ADFS)—simply because they are both Microsoft products.
Organizations using ADFS for SSO face complex configuration requirements and dependency on other resources to meet the minimum requirements for an SSO solution.
For further reference, please consider the following sections:
- Official Apache Maven documentation
- Spring Boot Maven Plugin Reference Guide
- Spring Web
- Spring Security
- Spring Boot Actuator
- Rest Repositories
The following guides illustrate how to use some features concretely:
- Building a RESTful Web Service
- Serving Web Content with Spring MVC
- Building REST services with Spring
- Securing a Web Application
- Spring Boot and OAuth2
- Authenticating a User with LDAP
- Building a RESTful Web Service with Spring Boot Actuator
- Accessing JPA Data with REST
- Accessing Neo4j Data with REST
- Accessing MongoDB Data with REST