make redirect resolver configureable by endpoint config

[etwillbefine]

Actually its hard to customise the RedirectResolver for the corresponding AuthorizationEndpoint (at least for my setup?).

For example I have one config AuthorizationServerConfiguration which extends AuthorizationServerConfigurerAdapter and configures the AuthorizationEndpoint using configure(AuthorizationServerEndpointsConfigurer configurer)

At the moment I'm not able to pass in a RedirectResolver to the configurer. Since I'm also configuring a CompositeTokenGranter which requires the AuthorizationEndpoint I'm also not able to inject the endpoint and call setRedirectResolver. Even when using PostConstruct it wont work until I create a separate configuration class for this. All dependencies (required by AuthorizationServerConfiguration) are initialised in one configuration (AuthorizationEndpoint doesnt exist at this point) and using PostConstruct in my AuthorizationServerConfiguration causes a cyclic dependency.

The only way I see is to create my own AuthorizationEndpoint based on the existing one and use a qualifier/primary for my custom one...

Is there maybe a straight forward way to set the redirect resolver without that change? I'd love to make it possible to configure it by using the AuthorizationServerEndpointsConfigurer. Thanks

(actually I've no clue whats wrong with the tests at travis .. :/)

[pivotal-issuemaster]

@etwillbefine Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-issuemaster]

@etwillbefine Thank you for signing the Contributor License Agreement!

[etwillbefine]

Is that something which could/will be merged or not?

[jgrandja]

Thanks for the PR @etwillbefine.
I applied some minor polish and merged to master.
Scheduled for 2.3.0.RC1 on Feb 27.

[etwillbefine]

Thanks for taking care!