|
| 1 | +<?php |
| 2 | + |
| 3 | +return $settings = array ( |
| 4 | + // If 'strict' is True, then the PHP Toolkit will reject unsigned |
| 5 | + // or unencrypted messages if it expects them signed or encrypted |
| 6 | + // Also will reject the messages if not strictly follow the SAML |
| 7 | + // standard: Destination, NameId, Conditions ... are validated too. |
| 8 | + 'strict' => false, |
| 9 | + |
| 10 | + // Enable debug mode (to print errors) |
| 11 | + 'debug' => false, |
| 12 | + |
| 13 | + // Service Provider Data that we are deploying |
| 14 | + 'sp' => array ( |
| 15 | + // Identifier of the SP entity (must be a URI) |
| 16 | + 'entityId' => '', |
| 17 | + // Specifies info about where and how the <AuthnResponse> message MUST be |
| 18 | + // returned to the requester, in this case our SP. |
| 19 | + 'assertionConsumerService' => array ( |
| 20 | + // URL Location where the <Response> from the IdP will be returned |
| 21 | + 'url' => '', |
| 22 | + // SAML protocol binding to be used when returning the <Response> |
| 23 | + // message. Onelogin Toolkit supports for this endpoint the |
| 24 | + // HTTP-Redirect binding only |
| 25 | + 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST', |
| 26 | + ), |
| 27 | + // Specifies info about where and how the <Logout Response> message MUST be |
| 28 | + // returned to the requester, in this case our SP. |
| 29 | + 'singleLogoutService' => array ( |
| 30 | + // URL Location where the <Response> from the IdP will be returned |
| 31 | + 'url' => '', |
| 32 | + // SAML protocol binding to be used when returning the <Response> |
| 33 | + // message. Onelogin Toolkit supports for this endpoint the |
| 34 | + // HTTP-Redirect binding only |
| 35 | + 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', |
| 36 | + ), |
| 37 | + // Specifies constraints on the name identifier to be used to |
| 38 | + // represent the requested subject. |
| 39 | + // Take a look on lib/Saml2/Constants.php to see the NameIdFormat supported |
| 40 | + 'NameIDFormat' => 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress', |
| 41 | + |
| 42 | + // Usually x509cert and privateKey of the SP are provided by files placed at |
| 43 | + // the certs folder. But we can also provide them with the following parameters |
| 44 | + 'x509cert' => '', |
| 45 | + 'privateKey' > '', |
| 46 | + ), |
| 47 | + |
| 48 | + // Identity Provider Data that we want connect with our SP |
| 49 | + 'idp' => array ( |
| 50 | + // Identifier of the IdP entity (must be a URI) |
| 51 | + 'entityId' => '', |
| 52 | + // SSO endpoint info of the IdP. (Authentication Request protocol) |
| 53 | + 'singleSignOnService' => array ( |
| 54 | + // URL Target of the IdP where the SP will send the Authentication Request Message |
| 55 | + 'url' => '', |
| 56 | + // SAML protocol binding to be used when returning the <Response> |
| 57 | + // message. Onelogin Toolkit supports for this endpoint the |
| 58 | + // HTTP-POST binding only |
| 59 | + 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', |
| 60 | + ), |
| 61 | + // SLO endpoint info of the IdP. |
| 62 | + 'singleLogoutService' => array ( |
| 63 | + // URL Location of the IdP where the SP will send the SLO Request |
| 64 | + 'url' => '', |
| 65 | + // SAML protocol binding to be used when returning the <Response> |
| 66 | + // message. Onelogin Toolkit supports for this endpoint the |
| 67 | + // HTTP-Redirect binding only |
| 68 | + 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', |
| 69 | + ), |
| 70 | + // Public x509 certificate of the IdP |
| 71 | + 'x509cert' => '', |
| 72 | + /* |
| 73 | + * Instead of use the whole x509cert you can use a fingerprint |
| 74 | + * (openssl x509 -noout -fingerprint -in "idp.crt" to generate it) |
| 75 | + */ |
| 76 | + // 'certFingerprint' => '', |
| 77 | + ), |
| 78 | +); |
0 commit comments