This handler is part of the light-hybrid-4j which is built on top of light-4j but focused on hybrid style of API only.
It supports OAuth2 with JWT token distributed verification and can be extended to other authentication and authorization approaches.
This is the handler that is injected during server startup if security.yml enableVerifyJwt is true. It does further scope verification if enableVerifyScope is true against hybrid schema specification.
From release 1.5.18, the light platform supports multiple chains of middleware handlers and multiple frameworks mixed in the same service instance. To have a security configuration file for different frameworks, a new hybrid-security.yml with the same content has been introduced. The security.yml is still loaded if hybrid-security.yml doesn’t exist for backward compatibility.
Here is an example of hybrid-security.yml
# Security configuration for hybrid-security in light-hybrid-4j. It is a specific config
# for Hybrid framework security. It is introduced to support multiple frameworks in the
# same server instance. If this file cannot be found, the generic security.yml will be
# loaded for backward compatibility.
# Enable JWT verification flag.
# Enable JWT scope verification. Only valid when enableVerifyJwt is true.
# User for test only. should be always be false on official environment.
# JWT signature public certificates. kid and certificate path mappings.
# Enable or disable JWT token logging
# Enable or disable client_id, user_id and scope logging.
# Enable JWT token cache to speed up verification. This will only verify expired time
# and skip the signature verification as it takes more CPU power and long time.
# If you are using light-oauth2, then you don't need to have oauth subfolder for public
# key certificate to verify JWT token, the key will be retrieved from key endpoint once
# the first token is arrived. Default to false for dev environment without oauth2 server
# or official environment that use other OAuth 2.0 providers.
Distributed JWT verification
Unlike simple web token that the resource server has to contact Authorization server to validate the bearer token. JWT can be verified by resource server as long as the token signing certificate is available at resource server.