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.

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

Ability to copy/paste SAML metadata from IdP without manipulation and have it work in yaml/gitops #26614

Open
allenhouchins opened this issue Feb 26, 2025 · 0 comments
Labels
:product Product Design department (shows up on 🦢 Drafting board)

Comments

@allenhouchins
Copy link
Member

Problem

I am not able to directly copy and paste my SAML metadata from my IdP and use it in yaml/gitops as yaml has strict tabbing requirements. This means I have to tab this data out before using it in yaml. Since sso_settings.metadata and mdm.end_user_authentication.metadata are at different indentations in yaml, this makes it more confusing on how to properly tab this data.

More info: fleetdm/confidential#9204 and #26042 and #26135

What have you tried?

I have tried to copy/paste my SAML metadata from IdP into a GitHub secret to use in yaml. This fails because the data is not properly tabbed so I encounter unfurl errors when gitops runs.

Potential solutions

You can copy/paste the data in the UI then through fleetctl export it to properly formatted yaml.

It would be great if we knew how to take this data provided in the GitHub secret and unfurl it for the customer automatically at run-time.

What is the expected workflow as a result of your proposal?

I can copy/paste my SAML metadata without manipulation, manage the configuration with gitops, and my admins and end users can authenticate successfully.

@allenhouchins allenhouchins added the :product Product Design department (shows up on 🦢 Drafting board) label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:product Product Design department (shows up on 🦢 Drafting board)
Projects
None yet
Development

No branches or pull requests

1 participant