Identity and people
OneLogin
Connect using the SAML Custom Connector (Advanced).
Use SAML Custom Connector (Advanced), previously called SAML Test Connector (Advanced). Have your Diakrin setup packet ready.
Create the application
- In OneLogin administration, add SAML Custom Connector (Advanced) and name it Diakrin.
- Open Configuration and enter the values below. The worksheet at the bottom of this guide generates an exact ACS validator.
- Under Parameters, include the work email as the SAML
emailattribute. Set Email NameID to the same value or agree a stable Persistent identifier. - Assign the pilot users or group and review your MFA policy.
Map the fields
| OneLogin field | Value |
|---|---|
| Audience (EntityID) | Diakrin SP Entity ID |
| Recipient | Diakrin ACS URL |
| ACS (Consumer) URL | Diakrin ACS URL |
| ACS (Consumer) URL Validator | Exact escaped ACS URL, anchored with ^ and $ |
| Login URL | Diakrin console sign-in URL |
| SAML initiator | Service Provider for the console-started pilot |
| SAML nameID format | Email or agreed Persistent identifier |
Do not use a wildcard ACS validator. Choose an application-specific issuer so separate customer connections do not accidentally reuse a generic issuer.
Activate and test
Export the application’s identity-provider SAML metadata and return it with approved domains and certificate expiry to your Diakrin onboarding contact. Leave Single Logout unconfigured; this flow does not guarantee global logout. After activation, follow Test and roll out SSO.
Official reference: Advanced SAML Custom Connector ↗.