[SAML Configuration] SAML settings

[mhawryluk]

Explanation of Change

Migrates SAML settings page to New Expensify. Allows enabling/disabling SAML, setting it as required, displaying the metadata (including Okta SCIM token) and setting Identity Provider metadata. Settings are located in the domain page and are accessible for admins and for verified domains only.

Fixed Issues

$ #72813
PROPOSAL: N/A

Tests

1. Log into an Expensify account that is an admin of a verified domain
2. Navigate to “Workspaces”
3. Click on the three dot menu. There should be one item: "go to domain".
4. Click on the row containing your verified domain
5. Verify you see a SAML tab (or initial page on mobile)
6. Click into the SAML tab if it is not already selected
7. Verify you see the option to enable SAML login
8. Enable SAML login
9. Verify that the switch for requiring login, as well as the domain configuration section, only appear when SAML login is enabled
10. Click on the Identity Metadata row.
11. Verify you see a right-docked modal with an area to add your SAML Identity Metadata
12. Enter some invalid text for your identity metadata and click "Save"
13. Verify you see an error indicating the metadata is invalid
14. Enter valid metadata for your SAML configuration and click “Save”
15. Verify you can click in and open your Identity Metadata section again
16. The copyable fields are all copyable, but not editable
17. Verify the large copyable field is extendable
18. You should see a button with Reveal Token in the Okta Scim Token section only if SAML is required and Okta is enabled for the domain by support.
19. Click "Reveal Token". Verify your OKTA SCIM token is revealed.
20. Log out of your account and try to sign back in
21. Verify: You’re given the option to sign in via SSO or via magic code
22. Sign in via SSO
23. Navigate to Workspaces > [Your Domain] > SAML and Require SAML on your domain
24. Log out of your account and try to sign back in
25. Verify you’re required to use SSO to sign in
26. Verify you’re able to sign in successfully.

Offline tests

1. Go Offline
2. Navigate to the “Workspaces” tab
3. Click on your domain in the list
4. Open the “SAML” tab if it is not already displayed
5. Verify you can see the SAML configuration settings for your domain
6. Click on the text field component for your Identity Metadata
7. Verify: The “submit” button is inactionable
8. Toggle the enable and require toggles for SAML
9. Verify: You are able to toggle these values
10. Come back online
11. Verify your SAML settings reflect your last toggle

QA Steps

Same as tests.

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message: https://swmansion.slack.com/archives/C01GTK53T8Q/p1763563249805809
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Nagranie.z.ekranu.2025-11-21.o.12.34.33.mov

Android: mWeb Chrome

Nagranie.z.ekranu.2025-11-21.o.12.08.01.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.16.Pro.Max.-.2025-11-21.at.12.02.33.mp4

Simulator.Screen.Recording.-.iPhone.16.Pro.Max.-.2025-11-21.at.12.54.53.mp4

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.16.Pro.Max.-.2025-11-21.at.12.00.01.mp4

MacOS: Chrome / Safari

Nagranie.z.ekranu.2025-11-21.o.12.03.47.mov

saml-login-1.mov

Nagranie.z.ekranu.2025-11-21.o.16.01.10.mov

Nagranie.z.ekranu.2025-11-21.o.16.20.24.mov

MacOS: Desktop

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/ONYXKEYS.ts	100.00% <ø> (ø)
src/components/Button/index.tsx	89.92% <ø> (ø)
src/components/Icon/chunks/illustrations.chunk.ts	0.00% <ø> (ø)
src/components/MenuItem.tsx	86.59% <100.00%> (ø)
src/components/TextPicker/index.tsx	0.00% <ø> (ø)
src/libs/API/types.ts	100.00% <ø> (ø)
src/pages/domain/BaseDomainVerifiedPage.tsx	0.00% <ø> (ø)
src/pages/domain/SamlDomainVerifiedPage.tsx	0.00% <ø> (ø)
src/pages/domain/WorkspacesDomainVerifiedPage.tsx	0.00% <ø> (ø)
src/styles/index.ts	45.65% <ø> (ø)
... and 15 more
... and 124 files with indirect coverage changes

[NikkiWines]

Just a couple function doc updates, otherwise looks great

[NikkiWines]

Suggested change

	* Sets logging in through SAML as required or not for the emails belonging to the domain
	* Sets whether logging in via SAML is required for the domain

[NikkiWines]

Suggested change

	* Sets logging in through SAML as enabled/disabled for the emails belonging to the domain
	* Sets whether logging in via SAML is enabled for the domain

[NikkiWines]

[melvin-bot]

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[mountiny]

Not Emergency, checks were not failing, must be some race condition in this case

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.65-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[kavimuru]

@mhawryluk @mountiny @NikkiWines could you help with Okta scim in the following steps?

You should see a button with Reveal Token in the Okta Scim Token section only if SAML is required and Okta is enabled for the domain by support.
Click "Reveal Token". Verify your OKTA SCIM token is revealed.

[NikkiWines]

@kavimuru I can generate the OKTA token for you. Which domain are you guys are using and which account are you testing with?

[kavimuru]

@NikkiWines this was the account used applausetester@applause.expensifail.com

[NikkiWines]

DM'd 1:1 to work through this as it requires some toggling with SAML required and generating the tokens

[OSBotify]

🚀 Deployed to production by https://github.com/marcaaron in version: 9.2.65-6 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅