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

Add end user's IdP information to host vitals #23236

Open
15 tasks
noahtalerman opened this issue Oct 25, 2024 · 2 comments
Open
15 tasks

Add end user's IdP information to host vitals #23236

noahtalerman opened this issue Oct 25, 2024 · 2 comments
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-numa customer-starchik #g-mdm MDM product group story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Oct 25, 2024

Goal

User story
As an IT admin,
I want to add end user's info (e.g. email, username, role, department) from the identity provider (IdP) to host vitals
so that I can identify which end user is assigned to each host.

Key result

Fleet users can add host vitals from their IdP as variables in configuration profiles

Original requests

#21028

Context

@marko-lisica: LDAP research document

Changes

Product

  • UI changes: Figma link
  • CLI (fleetctl) usage changes: No changes.
  • YAML changes: No changes.
  • REST API changes: [API changes] Add end user's IdP information to host vitals #23839
  • Fleet's agent (fleetd) changes: No changes.
  • Activity changes: TODO
  • Permissions changes: TODO
  • Changes to paid features or tiers: Available in Fleet Premium only.
  • Other reference documentation changes: No changes.
  • Once shipped, requester has been notified

Engineering

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

  • Requires load testing: TODO
  • Risk level: Low / High TODO
  • Risk description: TODO

Manual testing steps

  1. Step 1
  2. Step 2
  3. Step 3

Testing notes

Confirmation

  1. Engineer (@____): Added comment to user story confirming successful completion of QA.
  2. QA (@____): Added comment to user story confirming successful completion of QA.
@noahtalerman noahtalerman added story A user story defining an entire feature #g-mdm MDM product group :product Product Design department (shows up on 🦢 Drafting board) labels Oct 25, 2024
@marko-lisica marko-lisica changed the title Add end user's IdP group to host vitals Add end user's IdP information to host vitals Nov 4, 2024
@noahtalerman
Copy link
Member Author

Hey @marko-lisica, left some feedback in a Loom video here.

@nonpunctual nonpunctual added ~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-starchik labels Nov 12, 2024
@nonpunctual
Copy link
Contributor

related: #21028

@noahtalerman noahtalerman added Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. and removed Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. labels Nov 12, 2024
@noahtalerman noahtalerman added ~feature fest Will be reviewed at next Feature Fest and removed ~feature fest Will be reviewed at next Feature Fest labels Nov 14, 2024
@marko-lisica marko-lisica removed their assignment Nov 19, 2024
@marko-lisica marko-lisica removed the :product Product Design department (shows up on 🦢 Drafting board) label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-numa customer-starchik #g-mdm MDM product group story A user story defining an entire feature
Development

No branches or pull requests

4 participants