Hi @jzheaux

Started working on this and 6723 issues and it would be helpful to get some direction from your end. Looking through your PR PR 6563

Added

@FunctionalInterface
public interface ReactiveAuthenticationManagerResolver<C> {
	Mono<ReactiveAuthenticationManager> resolve(C context);
}

The Reactive equivalent of OAuth2ResourceServerConfigurer is ServerHttpSecurity.OAuth2ResourceServerSpec? Is that correct? Curious what is the design decision behind ServerHttpSecurity which contains many nested classes? 🤔
Declared the ReactiveAuthenticationManagerResolver in ServerHttpSecurity.OAuth2ResourceServerSpec parametrizing it with ServerHttpRequest and added the following

public OAuth2ResourceServerSpec reactiveAuthenticationManagerResolver(
		ReactiveAuthenticationManagerResolver<ServerHttpRequest> reactiveAuthenticationManagerResolver) {
	Assert.notNull(reactiveAuthenticationManagerResolver, "reactiveAuthenticationManagerResolver cannot be null");
	this.reactiveAuthenticationManagerResolver = reactiveAuthenticationManagerResolver;
	return this;
}

The changes to the configure method of ServerHttpSecurity.OAuth2ResourceServerSpec is a little tricky as I am struggling to understand the Reactive equivalent of BearerTokenAuthenticationFilter. Could be BearerTokenServerWebExchangeMatcher?
Your PR includes a sample boot oauth2-resourceservier-multitenancy. What is the requirement for the Reactive equivalent? Update existing/Add new one/Do nothing?🤔

I have read a few articles and Spring blogs on Reactive programming and I feel like I could use some more. Do you recommend any resource/tutorial/sample/article that could help me understand the Spring Reactive in deeper level?

Thank you for your usual support 🙂

Raf.

Multi-tenancy for Reactive Resource Server #6727

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions