[ https://issues.apache.org/jira/browse/CAUSEWAY-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854256#comment-17854256 ]
Daniel Keir Haywood commented on CAUSEWAY-3723: ----------------------------------------------- renamed; the original intent of this now moved to CAUSEWAY-3777 > Don't require a PasswordEncoder if secman's authenticator isn't actually > required. > ---------------------------------------------------------------------------------- > > Key: CAUSEWAY-3723 > URL: https://issues.apache.org/jira/browse/CAUSEWAY-3723 > Project: Causeway > Issue Type: Improvement > Components: Ext Sec Secman > Affects Versions: 2.0.0 > Reporter: Daniel Keir Haywood > Assignee: Daniel Keir Haywood > Priority: Minor > Fix For: 2.2.0 > > > CAUSEWAY-3700 provided an AutoConfiguration for secman's authenticator, but > it seems that its implementation requires a PasswordEncoder even if the > AutoConfiguration isn't actually activated. > I'm guessing that injecting a Provider<PasswordEncoder> might solve this. -- This message was sent by Atlassian Jira (v8.20.10#820010)