Robert Ratliff

I'm replacing a spring-security-oauth2 implementation. We had written our own register API and had a "subject" claim, which we later populated in the `sub` claim in the OAuth token. So...

I was thinking of using the clientSettings. Then I have access to it in `RegisteredClientRepository`. Example: ``` public class SubjectAwareRegisteredClientConverter extends DefaultRegisteredClientConverter { public static final String CLIENT_SETTINGS_SUBJECT_KEY = "subject";...

I found a workaround. Using the original poster's example: ``` public class AnotherClass { private final SomeClass repo; public AnotherClass(SomeClass repo) { this.repo = Objects.requireNonNull(repo, "repo"); } } ``` It...

Yes, that would work. Alternately it could be a constructor parameter. But a setter method would work as well.

Like others, I already had a `@Bean DynamoDBMapperConfig` defined. For me a combination of removing `dynamoDBMapperConfigRef` from the `@EnableDynamoDBRepositories annotation` and also marking my existing `DynamoDBMapperConfig` bean definition as `@Primary`...