Lines Matching refs:in
36 If you believe you have discovered a security vulnerability in this toolkit, please report it at ht…
51 and most security conscious enterprises in the world rely on.
83 the final app, the toolkit delegate session in the final app.
119 structure so take your time to locate the PHP SAML toolkit in the best place).
122 Take in mind that the compressed file only contains the main files.
139 …pass the settings as an array directly to the constructor (explained later in this document). If y…
146 The old code that you used in order to add SAML support will continue working
202 Or also we can provide those data in the setting file at the `$settings['sp']['x509cert']`
205 Sometimes we could need a signature on the metadata published by the SP, in
209 Use `sp_new.crt` if you are in a key rollover process and you want to
227 are described in a later section.
245 files when adding SAML support to your applications. Take in mind that those
258 * `settings_example.php` - A template to be used in order to create a
260 * `advanced_settings_example.php` - A template to be used in order to create a
283 and in some cases, configure advanced security issues like signatures and
321 // returned to the requester, in this case our SP.
347 // returned to the requester, in this case our SP.
404 * Instead of use the whole x509cert you can use a fingerprint in order to
407 * (openssl x509 -noout -fingerprint -in "idp.crt" to generate it,
410 * If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to
510 // Set to false and no AuthContext will be sent in the AuthNRequest.
568 // Organization information template, the info in en_US lang is
593 by the toolkit if no other array with settings info is provided in the constructor of the toolkit. …
607 You can declare the `$settingsInfo` in the file that contains the constructor
608 execution or locate them in any file and load the file in order to get the
609 array available as we see in the following example:
624 file located on the base folder of the toolkit. You can load this file in this
639 in addition to the the `_toolkit_loader.php`.
669 … Service of the SP with this information. If we do not set a `'url'` param in the login method and…
681 * `$parameters` - An array of parameters that will be added to the `GET` in the HTTP-Redirect.
702 provides examples of those views in the endpoints directory.
706 This code will provide the XML metadata file of our SP, based on the info that we provided in the s…
753 session_start(); // IMPORTANT: This is required in order to be able
754 // to store the user data in the session.
815 It also verifies that the user is authenticated and stored the userdata in session.
819 1. If no `RelayState` is provided, we could show the user data in this view
824 Notice that we saved the user data in the session before the redirection to
836 With this method we get all the user data provided by the IdP in the Assertion
882 no attributes in the SAML assertion, an empty array will be
895 session_start(); // IMPORTANT: This is required in order to be able
1021 * `$nameIdFormat` - The NameID Format will be set in the LogoutRequest.
1022 * `$nameIdNameQualifier` - The NameID NameQualifier will be set in the LogoutRequest.
1023 * `$nameIdSPNameQualifier` - The NameID SP NameQualifier will be set in the LogoutRequest.
1030 If we do not set a `'url'` param in the logout method and are using the
1087 Note: Review the `demo1` folder that contains that use case; in a later section we
1088 explain the demo1 use case further in detail.
1180 // put SAML settings into an array to avoid placing files in the
1206 php-saml toolkit uses a bunch of methods in OneLogin_Saml2_Utils that try to guess the URL where th…
1216 getSelfURLNoQuery and getSelfRoutedURLNoQuery are used to calculate the currentURL in order to vali…
1290 A simple class used to build the Setting object used in the v1.0 of the toolkit.
1322 that we defined in our SSO Request.
1509 Demos included in the toolkit
1520 The Onelogin's PHP Toolkit allows you to provide the settings info in two ways:
1526 In this demo we provide the data in the second way, using a setting array named
1528 to create the `settings.php` settings and store it in the `demo1/` folder.
1532 file is loaded in order to get the `$settingsInfo` var to be used in order to initialize
1535 Notice that in this demo, the `setting.php` file that could be defined at the base
1553 2.1 in the first link, we access to (`index.php?sso`) an `AuthNRequest`
1559 2.2 in the second link we access to (`attrs.php`) have the same process
1562 3. The SAML Response is processed in the ACS (`index.php?acs`), if the Response
1566 4. We are logged in the app and the user attributes are showed.
1595 The Onelogin's PHP Toolkit allows you to provide the settings info in two ways:
1607 use the files located in the endpoint folder (`acs.php` and `sls.php`).
1623 in the toolkit (`acs.php`, `sls.php` of the endpoints folder). This demo2 uses
1628 The SAML workflow that take place is similar that the workflow defined in the
1634 ACS endpoint, in this case `acs.php` of the endpoints folder.
1636 2. The SAML Response is processed in the ACS, if the `Response` is not valid,
1639 user is logged and redirects to `index.php`, so we will be in the
1703 handle SLO in this demo-old.