Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OIDC (Okta) issue with using callback handler for AWS_IAM_MSK #642

Open
4 tasks done
ivanbishop opened this issue Oct 30, 2024 · 5 comments
Open
4 tasks done

OIDC (Okta) issue with using callback handler for AWS_IAM_MSK #642

ivanbishop opened this issue Oct 30, 2024 · 5 comments
Labels
status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/bug Something isn't working

Comments

@ivanbishop
Copy link

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

See https://discord.com/channels/897805035122077716/1298004148066848849
Validate with Okta works OK, but om submit I get a 500 error.
logit.txt
YML-config-compose.zip

Expected behavior

Validate works on adding a new cluster but I expect Submit to work

Your installation details

Run via (compose in ZIP)
docker-compose -f ~/kui/docker-compose.yml up -d
and the external rbac file in ZIP too

Steps to reproduce

launch container, try and configure a new cluster

Screenshots

No response

Logs

logit.txt

Additional context

No response
@ivanbishop ivanbishop added status/triage Issues pending maintainers triage type/bug Something isn't working labels Oct 30, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Oct 30, 2024
@github-actions GitHub Actions
Copy link

Hi ivanbishop! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

@kothapet
Copy link

kothapet commented Nov 15, 2024 •
edited
Loading

@ivanbishop,

OKTA sso with MSK IAM works fine. I have this running.

Looks like you have an extra semicolon ; at the end of client.callback.handler.class line. Remove it.
Only jass.config needs semicolon ; at the end.

You have

KAFKA_CLUSTERS_0_PROPERTIES_SASL_CLIENT_CALLBACK_HANDLER_CLASS: software.amazon.msk.auth.iam.IAMClientCallbackHandler;

Make it

KAFKA_CLUSTERS_0_PROPERTIES_SASL_CLIENT_CALLBACK_HANDLER_CLASS: software.amazon.msk.auth.iam.IAMClientCallbackHandler

And that should work.

@ivanbishop
Copy link
Author

ivanbishop commented Nov 18, 2024 via email

@kothapet
Copy link

I looked at your config and compared to mine, and pretty much same except
I dont have jwk-set-uri in okta config
I have given permissions to consumer as you will to browse the topics.
I have additional glue serde, and audit settings but those are optional.

Which servers are you getting 500 errors from? from kafkaui or okta? it seems from the logs authentication is working and its sending the group kafbat-admins back.

@ivanbishop
Copy link
Author

ivanbishop commented Nov 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ivanbishop @kothapet