芝麻web文件管理V1.00
编辑当前文件:/home/mgatv524/public_html/avenida/views/onelogin.zip
PK sqY4d d php-saml/settings_example.phpnu [ true, // Enable debug mode (to print errors) 'debug' => false, // Set a BaseURL to be used instead of try to guess // the BaseURL of the view that process the SAML Message. // Ex. http://sp.example.com/ // http://example.com/sp/ 'baseurl' => null, // Service Provider Data that we are deploying 'sp' => array( // Identifier of the SP entity (must be a URI) 'entityId' => '', // Specifies info about where and how the
message MUST be // returned to the requester, in this case our SP. 'assertionConsumerService' => array( // URL Location where the
from the IdP will be returned 'url' => '', // SAML protocol binding to be used when returning the
// message. Onelogin Toolkit supports for this endpoint the // HTTP-POST binding only 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST', ), // If you need to specify requested attributes, set a // attributeConsumingService. nameFormat, attributeValue and // friendlyName can be omitted. Otherwise remove this section. "attributeConsumingService"=> array( "serviceName" => "SP test", "serviceDescription" => "Test Service", "requestedAttributes" => array( array( "name" => "", "isRequired" => false, "nameFormat" => "", "friendlyName" => "", "attributeValue" => "" ) ) ), // Specifies info about where and how the
message MUST be // returned to the requester, in this case our SP. 'singleLogoutService' => array( // URL Location where the
from the IdP will be returned 'url' => '', // SAML protocol binding to be used when returning the
// message. Onelogin Toolkit supports for this endpoint the // HTTP-Redirect binding only 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', ), // Specifies constraints on the name identifier to be used to // represent the requested subject. // Take a look on lib/Saml2/Constants.php to see the NameIdFormat supported 'NameIDFormat' => 'urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified', // Usually x509cert and privateKey of the SP are provided by files placed at // the certs folder. But we can also provide them with the following parameters 'x509cert' => '', 'privateKey' => '', /* * Key rollover * If you plan to update the SP x509cert and privateKey * you can define here the new x509cert and it will be * published on the SP metadata so Identity Providers can * read them and get ready for rollover. */ // 'x509certNew' => '', ), // Identity Provider Data that we want connect with our SP 'idp' => array( // Identifier of the IdP entity (must be a URI) 'entityId' => '', // SSO endpoint info of the IdP. (Authentication Request protocol) 'singleSignOnService' => array( // URL Target of the IdP where the SP will send the Authentication Request Message 'url' => '', // SAML protocol binding to be used when returning the
// message. Onelogin Toolkit supports for this endpoint the // HTTP-Redirect binding only 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', ), // SLO endpoint info of the IdP. 'singleLogoutService' => array( // URL Location of the IdP where the SP will send the SLO Request 'url' => '', // URL location of the IdP where the SP SLO Response will be sent (ResponseLocation) // if not set, url for the SLO Request will be used 'responseUrl' => '', // SAML protocol binding to be used when returning the
// message. Onelogin Toolkit supports for this endpoint the // HTTP-Redirect binding only 'binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect', ), // Public x509 certificate of the IdP 'x509cert' => '', /* * Instead of use the whole x509cert you can use a fingerprint in * order to validate the SAMLResponse, but we don't recommend to use * that method on production since is exploitable by a collision * attack. * (openssl x509 -noout -fingerprint -in "idp.crt" to generate it, * or add for example the -sha256 , -sha384 or -sha512 parameter) * * If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to * let the toolkit know which Algorithm was used. Possible values: sha1, sha256, sha384 or sha512 * 'sha1' is the default value. */ // 'certFingerprint' => '', // 'certFingerprintAlgorithm' => 'sha1', /* In some scenarios the IdP uses different certificates for * signing/encryption, or is under key rollover phase and more * than one certificate is published on IdP metadata. * In order to handle that the toolkit offers that parameter. * (when used, 'x509cert' and 'certFingerprint' values are * ignored). */ // 'x509certMulti' => array( // 'signing' => array( // 0 => '
', // ), // 'encryption' => array( // 0 => '
', // ) // ), ), ); PK sqY= php-saml/composer.jsonnu [ { "name": "onelogin/php-saml", "description": "OneLogin PHP SAML Toolkit", "license": "MIT", "homepage": "https://developers.onelogin.com/saml/php", "keywords": ["saml", "saml2", "onelogin"], "autoload": { "psr-4": { "OneLogin\\": "src/" } }, "support": { "email": "sixto.garcia@onelogin.com", "issues": "https://github.com/onelogin/php-saml/issues", "source": "https://github.com/onelogin/php-saml/" }, "require": { "php": ">=5.4", "robrichards/xmlseclibs": ">=3.0.4" }, "require-dev": { "php-coveralls/php-coveralls": "^1.0.2 || ^2.0", "phpunit/phpunit": "^4.8.35 || ^5.7 || ^6.5 || ^7.1", "sebastian/phpcpd": "^2.0 || ^3.0 || ^4.0", "phploc/phploc": "^2.1 || ^3.0 || ^4.0", "pdepend/pdepend": "^2.5.0", "squizlabs/php_codesniffer": "^3.1.1" }, "suggest": { "ext-openssl": "Install openssl lib in order to handle with x509 certs (require to support sign and encryption)", "ext-curl": "Install curl lib to be able to use the IdPMetadataParser for parsing remote XMLs", "ext-gettext": "Install gettext and php5-gettext libs to handle translations" } } PK sqY5Ce( ( php-saml/LICENSEnu [ Copyright (c) 2010-2016 OneLogin, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. PK sqYS:hC C &