Skip to content

SAML - The "Identity Provider MetaData" field is not expandable #76250

Closed

Description

@nlemma

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: v9.2.65-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74973
Email or phone of affected tester (no customers): applausetester@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome, Android 13 / Xiaomi Poco F5, iOS 15.8.3 / iPhone 7 Plus
App Component: Other

Action Performed:

  1. Navigate to https://staging.new.expensify.com/
  2. Log in with an account that is a domain admin
  3. Go to the “Workspaces” tab and scroll to the bottom of the page
  4. Tap on the three-dot menu in the domain applause.expensifail.com > Go to domain > SAML
  5. Toggle the "Enable SAML login" if still disable
  6. Click the "Identity Provider MetaData" option and RHP will open
  7. Try to expand the "Identity Provider MetaData" field

Expected Result:

The "Identity Provider MetaData" field is expandable

Actual Result:

The "Identity Provider MetaData" field is not expandable
Note:

  • In OD, the "Identity Provider MetaData" field is expandable

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7015011_1764260430314.76190_-_PR74973_-_SAML_-_The_Identity_Provider_MetaData_field_is_not_expandable.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 27, 2025
  2. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. github-actions commented on Nov 27, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    Triggered auto assignment to @MariaHCD (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. NikkiWines commented on Nov 27, 2025

    @NikkiWines
    Contributor

    Not a bug, this is intentional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions