Inbound SAML

Configures a custom Identity Provider that supports SAML 2.0. LoginRadius acts as the Service Provider, forwarding authentication requests to the configured SAML IDP.

Social & Federated Node

note

Child node: must be placed inside a Web Page node.

Node Card

Inbound SAML

true

false

Category: Social & Federated Nodes

Type: inbound-saml

Placement: Child node inside a Web Page node.

---

Properties

Property	Type	Required	Description
SAML Provider	select	Yes	The configured inbound SAML provider to use. Populated from inbound SAML providers configured in the Identity Orchestration settings.

Outputs & Errors

Output	Condition
true	SAML 2.0 authentication succeeded and a linked LoginRadius account was resolved
false	SAML authentication failed, assertion validation failed, or no linked account could be resolved

---

Usage Notes

Use Inbound SAML to integrate enterprise Identity Providers such as Okta, Azure AD, or PingFederate via SAML 2.0. Configure the IDP metadata (Entity ID, SSO URL, X.509 certificate) and attribute mappings in the Identity Orchestration settings before referencing the provider here. LoginRadius's SP metadata (ACS URL, Entity ID) must be registered in the IDP configuration.