I’m using the OAuth2 community module with a custom connector and everything seems to work as expected with the exception of the URLMangler. In particular the links in the Layer Preview page show the expected custom key-value (access_token) pair but it’s followed by a “?” instead of the expected “&” before the remaining parameters (service, etc.). This causes an OWS:ExceptionReport (“No service: ( ows )”) when clicking the Layer Preview links.
https://geoserver.…/sf/ows?access_token=abc?service=WFS&version=1.0.0&request=GetFeature&typeName=sf:bugsites&maxFeatures=50
There doesn’t appear to be an issue with the custom URLMangler itself as it only adds the single access_token entry to the kvp map so I’m wondering if the issue is at a higher level (e.g. ResponseUtils#buildURL) or if the issue might be obvious to anyone else?