AuthorizationServerContext should be accessible in custom consent controller

[opcooc]

When implementing multi tenant based on stackoverflow, I need to implement TenantWebAuthenticationDetailsSource and TenantWebAuthenticationDetails during AuthorizationConsent to support tenant acquisition after 302. Can I provide custom parameter assembly in the sendAuthorizationConsent method to simplify this operation

[jgrandja]

@opcooc

I need to implement TenantWebAuthenticationDetailsSource and TenantWebAuthenticationDetails during AuthorizationConsent to support tenant acquisition

Can you please provide more details on why you need a custom WebAuthenticationDetails? How are you identifying tenants? Header, Sub-domain, etc..

Have you seen the How-to: Implement Multitenancy guide? It provides a complete sample without the need to customize the authorization consent process.

[opcooc]

@opcooc

我需要在 AuthorizationConsent 期间实现 TenantWebAuthenticationDetailsS​​ource 和 TenantWebAuthenticationDetails 以支持租户获取

您能否详细说明为什么需要自定义WebAuthenticationDetails？您如何识别租户？标头、子域等。

您是否看过《如何实施多租户》指南？它提供了完整的示例，无需自定义授权同意流程。

@jgrandja

Yes, I looked at [How-to: Implement Multitenancy] but can't get it after customizing the consentPage.

This is my sample，https://github.com/opcooc/demo-authorizationserver/blob/1f3294410113c05ea8bc164b70deacfa2bd4eed7/src/main/java/sample/web/AuthorizationConsentController.java#L63，
access [http://127.0.0.1:9443/server/oauth2/authorize?response_type=code&scope=profile openid&client_id=messaging-client&redirect_uri=http://127.0.0.1:8080/login/oauth2/code/messaging-client-oidc&state=8a0781548e7f76ae018e94e450982413] ，console output 'The issuer was not obtained'.

I don't know what went wrong. Can you help me find out? Thanks。

[jgrandja]

@opcooc The AuthorizationServerContext should be accessible in AuthorizationConsentController. This appears to be a bug. I'll look into this and get back to you shortly.