Header-auth not working properly #1013
-
Hello, I would like to use header-auth config as an "authorizer". So it looks like that This is what I log from the middleman :
And this is the piece of config I use in akhq akhq:
connections:
ass:
properties:
bootstrap.servers: <BROKERS URL>
security.protocol: SSL
dev:
properties:
bootstrap.servers: <BROKERS URL>
security.protocol: SSL
int:
properties:
bootstrap.servers: <BROKERS URL>
sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule required username=<USERNAME> password=<PASSWORD>;
sasl.mechanism: SCRAM-SHA-512
security.protocol: SASL_SSL
sandbox:
properties:
bootstrap.servers: <BROKERS URL>
security.protocol: SSL
security:
default-group: test-topic-reader
groups:
test-admin:
attributes:
connects-filter-regexp:
- .*
consumer-groups-filter-regexp:
- .*
topics-filter-regexp:
- .*
name: test-admin
roles:
- topic/read
- topic/insert
- topic/delete
- topic/config/update
- node/read
- node/config/update
- topic/data/read
- topic/data/insert
- topic/data/delete
- group/read
- group/delete
- group/offsets/update
- registry/read
- registry/insert
- registry/update
- registry/delete
- registry/version/delete
- acls/read
- connect/read
- connect/insert
- connect/update
- connect/delete
- connect/state/update
test-no-role:
name: test-no-role
roles: []
test-topic-reader:
attributes:
topics-filter-regexp:
- .*
name: test-topic-reader
roles:
- topic/read
header-auth:
default-group: test-topic-reader
groups:
- groups:
- test-admin
name: fed_identite@app_3625
groups-header: X-Forwarded-Groups
groups-header-separator: ','
ip-patterns:
- 0.0.0.0
user-header: X-Forwarded-Email
users:
- groups:
- test-admin
username: [email protected] For some reason I don't get, the role applied for all user tested will be test-topic-reader. I tried to activate debug trace as suggested in https://akhq.io/docs/debug.html#debugging-authentication, but I still don't see any related issue. Could you please assist me with this ? Thank you ! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Difficult to see the issue like that.
I've the feeling it's a case issue on header |
Beta Was this translation helpful? Give feedback.
Difficult to see the issue like that.
ip-patterns
remove it pleasemicronaut.server.netty.log-level
configuration to TRACE and enable more log withcurl -i -X POST -H "Content-Type: application/json" -d '{ "configuredLevel": "TRACE" }' http://localhost:28081/loggers/io.netty
I've the feeling it's a case issue on header