redacted redacted redacted
The JwtTokenVerifier is only available for these authentication types enabled: LOCAL, ACTIVE_DIRECTORY_LDAP, SAML, UAA_ACCESS_TOKEN. Therefore in your case this bean should not be initialized.
In case your project is using @ComponentScan in your project then TokenHandlingController get scanned always before UAA can do anything. In order to solve problem, please exclude TokenHandlingController (if you don’t need it) during the scanning.
@ComponentScan(basePackages = { "com.mgmtp.a12.uaa.authentication" }
,excludeFilters = @Filter(type = FilterType.ASSIGNABLE_TYPE, classes = TokenHandlingController.class)
)
Hope this helps.
redacted redacted redacted
As long as you can exclude the controller it’s fine because you actually don’t needed. I don’t know why in your project, the bean get scanned.
@tomas-thin-gale do you have an idea about @DataServicesApplication?
DS includes everything that is needed for local authentication. I was not aware that using this configuration clashes with other UAA configurations because DS does not test different UAA configurations.
@tuan-stable-gale please create a ticket to describe this scenario so we can see how we can avoid these scenarios or how to create integration tests for various UAA configurations in DS, WF and customer projects
redacted redacted redacted