shri-arunraj commented on issue #3189:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/3189#issuecomment-1184390736
@liubao68 I have an issue in that `CommonHttpDispatcher` can route to
registered third party micro service , but the auth handlers configured for the
third party microservice are not triggered if this dispatcher is used.
Can you help here? Why handlers are not triggered on using this dispatcher?
But for `URLMappedDispatcher` handlers are triggered but HTTP headers
received in the original request are not forwarded to the destination provider
on routing.
So with `CommonHttpDispatcher` auth handlers are not triggered where as with
`URLMappedDispatcher` headers are not forwarded to receipent.
Can you provide solution for either of these? Thanks in advance :)
This is my configuration
```
servicecomb-config-order: 100
servicecomb:
service:
application: m1-services
name: gateway
properties:
allowCrossApp: true #whether to allow calls across applications
version: 0.0.4
registry:
# Default using local service center
address: http://localhost:30100
instance:
watch: false
edge:
filter:
addHeader:
enabled: true
allowedHeaders: xxx
handler:
chain:
Consumer:
default: loadbalance,tracing-consumer
service:
mfa-login-service: authClientGrant,loadbalance,tracing-consumer
Provider:
default: bizkeeper-provider,tracing-provider
rest:
address: 0.0.0.0:9091?sslEnabled=false
tracing:
enabled: true
http:
dispatcher:
edge:
http:
enabled: true
order: 1
mappings:
oauthAdmin:
path: "/admin/oauth/.*"
microserviceName: oauth-service
prefixSegmentCount: 1
versionRule: 0.0.0+
mfaServices:
path: "/a/mfa/login/.*"
microserviceName: mfa-login-service
prefixSegmentCount: 1
versionRule: 0.0.0+
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
