SSOgen

SSOgen is a gateway-style SSO platform focused on bringing modern federation to legacy enterprise apps (notably Oracle E-Business Suite, PeopleSoft, JD Edwards, SAP). It can act as a SAML 2.0/1.1 IdP or SP gateway, front apps that don’t natively speak SAML/OIDC, and delegate authentication to external IdPs (e.g., Microsoft Entra ID, Okta, Ping). It also offers built-in MFA and an LDAP-backed user store.

Key Capabilities

• SAML gateway patterns (IdP/SP): Supports SAML 2.0 and 1.1; can register with external IdPs and front non-SAML apps (e.g., Oracle EBS/PeopleSoft/JDE/SAP).

• OpenID Connect gateway: Materials describe an OpenID Gateway and interoperability with popular IdPs (Okta, Entra ID, Ping, AD FS).

• MFA & desktop auth: Built-in MFA (mobile app, SMS, email) and references to Kerberos/desktop authentication via the SSO Server.

• Directory options: Dedicated LDAP (LDAPv3) user store and AD/LDAP integrations.

Limitations

• OIDC/OAuth depth: Public pages mention an OpenID Gateway, but there’s not enough public information to confirm full OIDC provider details (discovery, token endpoints, logout profiles) or advanced OAuth features (PAR, DPoP, mTLS)

• SCIM provisioning: Documentation emphasizes SAML/OIDC gating, LDAP, and MFA; not enough public information to confirm general-purpose SCIM 2.0 provider/consumer capabilities.

• Documentation maturity: Many materials are solution pages and product briefs; deep admin references (claims/headers, session cookies, failover) are limited.

• Operations footprint: Gateway insertion for legacy suites (EBS/PeopleSoft/JDE) adds components (plugins/agents, proxies, certificates) that you must deploy and maintain.

• Vendor size/roadmap: Third-party briefs (e.g., Thales) exist, but independent analyst coverage is scarce; assess vendor viability and support SLAs for mission-critical ERP access.