How JMIX handle code for AWS Cognito Access Token (user pool) for REST API JMIX

Support
#1

How JMIX handle code for AWS Cognito Access Token (user pool) for REST API JMIX ? Any samples or reference share will be helpful . Thanks

#4

Hi,

We haven’t tried the AWS Cognito for user authentication ourselves, but it seems that the OpenID Connect add-on can do the job. You can find information about how to use the add-on in the GitHub readme file.

#5

Hi,

Thank you for pointing me to the OpenID Connect add-on for AWS Cognito and its associated GitHub README. I’ve been reviewing the setup, and I have a specific question regarding the Spring Security properties.

In my current setup with Keycloak, I use spring.security.oauth2.client.provider.keycloak.user-name-attribute. Given the transition to AWS Cognito, would it be correct to replace that with spring.security.oauth2.client.provider.cognito.user-name-attribute? I want to ensure that the property naming convention aligns correctly with the AWS Cognito integration.

Any guidance or confirmation on this would be greatly appreciated.

Best regards,

Farid

#6

You can use any word at this place. “keycloak”, “cognito” or just “abcd” is a providerId necessary to group several settings together. Just don’t forget to use “cognito” in other properties keys as well. See Core Configuration :: Spring Security