miniOrange SAML SSO handles the protocol: Service Provider configuration, IdP metadata, attribute mapping, just-in-time provisioning. Every successful SAML response enriches wp_users and wp_usermeta with attributes like IdP identifier, department, group, mapped role, and last-login timestamp. If logging is enabled, every authentication writes a row to the SSO log table. The default WordPress Users screen shows almost none of that.

SleekView reads wp_users joined with the miniOrange SAML usermeta keys and the SSO log table as one workspace. One row per user (or one row per login, depending on the saved view) with IdP, mapped role, department, and last-login as filterable columns. Filter to IdP equals Azure AD and last-login before 30 days ago to find stale SSO users. Filter to mapped role equals administrator and IdP equals Okta to verify enterprise role mappings. Save the view and reopen it at access-review time.

The plugin keeps owning SAML responses, signature validation, and JIT provisioning. SleekView only adds the table-shaped reporting layer.

SAML SSO is one of the higher-investment integrations on WordPress and miniOrange makes it tractable. The trade-off is that the resulting metadata lives in usermeta and the admin surface has not kept pace. Every login enriches the WordPress database with attributes that could power a real identity roster, but the admin shows them one user at a time.

SleekView reads the SSO log and the SAML usermeta together and renders them as one sortable, filterable workspace. Access reviews become a saved view. Stale-user audits become a single sort.

The plugin keeps owning SAML end to end. The IT team gets the roster the integration always justified.