[oliverguenther]

Ticket

https://community.openproject.org/projects/OP/work_packages/OP-20460/activity

What are you trying to accomplish?

• Allow manually refreshing the SAML metadata
• Allow administrators to review the SAML metadata before applying it
• To avoid fetching the metadata twice, pass the options to the form, but use a verifying token to ensure the options have not been tampered with.

Screenshots

What approach did you choose and why?

AI involvement

Collaborative – AI generated a substantial part of the code; I reviewed and understand every line.

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)

[NobodysNightmare]

Has the placement of the "refresh metadata" button been aligned with UX?

I think we never added an interactive element in this position of the wizards yet and it feels wrong to me.

I'd probably put it in either of those places:

• inside the "metadata" menu entry
• in the side panel

The side panel has precedence to house "service buttons" in storages already, e.g. the "sync now" button for AMPF:

[psatyal]

Hi @oliverguenther, @NobodysNightmare:

Yes, I think it makes more sense to put it in the sidebar. There could be a Metadata section, right?

Title: Metadata
Text: You can check if the configuration fetched from your identity provider has changed.
Action: Refresh metadata

Thoughts?

Cheers
Parimal

[NobodysNightmare]

Had a few comments. I think none of them are blocking per se.