Jahia Oauth AWS Cognito

Invalidate previous session to login new user

Cache SSO_LOGIN in callback action

Remove protected url /userinfo

Decode OpenID Token in the callback

[WIP] Performance issues: cache user when retrieving membership

[WIP] Performance issues: get all groups and cache them

[WIP] Performance issues: remove search users & groups

• Always identify user with sub

• Remove logoutendpoint (duplicate endpoint)

• Expose provider key

• Clean code + Add logout configuration

• Expose AWS Cognito constants

• Expose user sub

• Verify user password
• FIX userinfo endpoint case sensitive
• Remove custom implementation
• Add provider and site key in aws configuration to get user in cache

• Improve performances caching all users
• Add AWS namespace (custom and dev prefix)
• Search user by sub
• Custom login parameters app & action

• Bad performance during search, hack with a specific lookup by email Thomas LE CLERE 4 minutes ago

• Review search as we can't filter with mutiple attributes neither with custom attributes 
• Generic user attributes

• Set endpoint, clientId, clientSecret in the user group provider
• Revert to username instead of sub (sub is a JCRUserNode property)
• Multiple AWS custom login services, we get the one found in installed… 
• Guess siteKey to custom login url
• Implement verify password checking if we can log in the user
• Replace attribute name with :

Custom logout JAX-RS endpoint

Search user by sub attribute

Get / Search users and groups recursively

Identify user by sub instead username
Fallback to systemsite when you get awsCognitoConfiguration
Add fr translations

Search users and groups
Expose client secret in the configuration Save the last connection date under a jcrusernode property
FIX Cache Manager with module name to avoid ClassCastException
Expose endpoint & clientID
FIX account locked property
Move constants to AwsCognitoConstants (remove custom logout)
Expose AWS Cognito configuration set up in site settings (withlogout UI in progress)
Expose OSGI interface to implement custom login service

Double implementation OIDC + custom login url

Fallback authentication config to systemsite if it's not found in current site

Catch AWS error

Add new external login page with the user encrypted in the callback