Topic starter
16/01/2026 2:50 pm
TL;DR: 2025 updates to Connect added federation-based application registration, JIT user provisioning, issuer validation, certificate rescans, and workflow changes that reduce onboarding friction while tightening configuration correctness across identity operations, according to Raidiam. The governance challenge is shifting from manual control to proving that federation, claims, and certificate states stay accurate at scale.
Editorial analysis by NHI Mgmt Group, based on content published by Raidiam: “Raidiam Connect 2025 Year in Review”.
Key questions
Q: How should teams govern federation-based application onboarding?
A: Treat onboarding as a trust decision, not just a registration task.
Q: Why does issuer uniqueness matter in federation and SSO workflows?
A: Issuer values identify who signs or vouches for tokens, so duplication creates ambiguity in validation and routing.
Q: What breaks when certificate state is not continuously revalidated?
A: Revocation can lag behind actual authority state, which leaves inactive certificates visible in the platform and available to dependent workflows.
Practitioner guidance
- Validate federation metadata before onboarding Require entity statements, entity configurations, and federation list references to be checked before an application is accepted into production trust paths.
- Enforce issuer uniqueness across authorisation servers Block any server configuration that reuses an issuer value so token validation and trust decisions remain unambiguous across the ecosystem.
- Make federation-specific role metadata mandatory Require entity type, claim name, operator, and data type before a role can be reused in any federation workflow.
Bottom line: Raidiam’s 2025 updates show that federation, issuer control, and certificate revalidation are now part of day-to-day identity governance.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
08/10/2026 4:42 pm
Federation is becoming the trust boundary for NHI governance. When application registration shifts into federation-based onboarding, the security question is no longer only who can create an object, but what evidence proves the object should be trusted. That moves governance upstream into metadata validation, issuer control, and claims alignment. Practitioners should treat federation policy as part of the identity control plane, not as a convenience layer.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: How do workflow controls help reduce onboarding errors for NHIs?
A: Guided workflows matter because they move validation to the point of entry. Inline checks, sequenced required fields, and immediate feedback reduce the chance that a server, certificate, or application is created with incomplete trust data. That is operationally important when onboarding volume increases and manual review no longer scales cleanly.
👉 Read our full editorial: Federation, onboarding and certificate controls tighten NHI governance