Public API: Migrate Settings from norman to steve auth configuration and actions #12331

[nwmac]

UI work for https://github.com/rancher/rancher-security/issues/1178

Update UI to use Steve Public API in place of Norman API.

Full details TBD

[github-actions]

🎯 Agentic Issue Triage

Summary: This issue tracks the migration of Settings-related UI from the Norman API to the Steve Public API, as part of a security initiative (rancher-security#1178). The full scope is TBD, so needs-scoping has been applied.

---

📋 Context & Related Issues

This issue is part of the broader Norman → Steve migration epic:

Issue	Title	Status
#10742	EPIC: Norman to Steve migration	open
#12331	Migrate from norman to steve auth configuration and actions	open (parent)
#15325	Migrate authconfigs from norman to steve	open
#16591	Migrate from norman to steve cloudcredentials	open
#12488	Migrate to new public api token endpoint	open

The security motivation is SURE-6548 / RFC 19 Token API Evolution.

🔍 Technical Area

Affected Code Areas:

• shell/utils/settings.ts — uses MANAGEMENT.SETTING (steve) already, but may have Norman-backed settings paths
• shell/config/types.ts — Norman and Steve type constants
• Auth settings pages under shell/pages/auth/ or similar
• Any component using v3/settings, v3/authConfigs, or v3-public/authproviders via Norman

Key Steve Equivalents to Investigate:

• Norman v3/settings → Steve management.cattle.io.settings
• Norman v3/authConfigs → Steve management.cattle.io.authconfigs (tracked in Migrate authconfigs from norman to steve #15325)
• The RFD for auth config migration: https://github.com/SUSE/rancher-architecture/pull/22

🛠️ Debugging & Investigation Strategies

1. Identify all Norman settings calls: Search the codebase for NORMAN.SETTING or direct references to /v3/settings endpoints.

   grep -r "NORMAN\|v3/settings\|normanSetting" shell/ --include="*.ts" --include="*.vue" -l

2. Compare Norman vs Steve setting schemas: Use Rancher API Explorer to compare /v3/settings (Norman) vs /v1/management.cattle.io.settings (Steve) to identify field mapping differences.

3. Check for dual-write / dual-read patterns: Some settings may be read from Norman and written to Steve or vice versa — look for inconsistencies in store usage.

4. Review the public auth settings page: The Settings UI pages may directly use Norman API — check shell/pages/ for pages related to auth settings.

5. Verify Steve API availability: Confirm which settings are available in the Steve API and whether the Steve schema exposes the same actions as Norman.

✅ Suggested Subtasks (once scoped)

• Audit all UI settings reads/writes currently using Norman API
• Map Norman settings resource fields to Steve equivalents
• Update store dispatches from norman/find* to management/find* for settings
• Migrate any Norman-based auth configuration calls to Steve endpoints
• Update E2E and unit tests to cover new API paths
• Verify no regressions on Settings UI pages after migration
• Coordinate with backend team on public API endpoint readiness (if not yet available)
• Reference the RFD (SUSE/rancher-architecture#22) for auth config migration patterns

🔗 Useful Resources

• Norman to Steve migration epic #10742
• Migrate authconfigs from norman to steve #15325 — useful patterns for this work
• SUSE rancher-architecture RFD #22 — blocked dependency for auth config migration
• [Rancher Dashboard Contributing Guide]((extensions.rancher.io/redacted)
• RFC 19: Token API Evolution

Generated by Agentic Triage for issue #17268 · ◷

[github-actions]

🤖 Issue grooming questions

The issue title and referenced work (#12331) give helpful context, but the description currently says "Full details TBD" — a few key details are needed before this can be scoped or assigned:

1. What does "done" look like? Please add 1–3 concrete acceptance criteria. For example: which specific settings pages or components will be migrated, and what does a successful migration look like to a user (e.g., "Settings page X uses the Steve API endpoint instead of the Norman endpoint, with all existing functionality preserved")?

2. Which settings are in scope? Are there specific settings pages, API calls, or UI components already identified for migration, or is that part of the investigative work for this issue?

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ◷