Lines Matching refs:file

122 Take in mind that the compressed file only contains the main files.
137 and settings file stored at `vendor/onelogin/php-saml`.
148 (notice that the `compatibility.php` file do that).
202 Or also we can provide those data in the setting file at the `$settings['sp']['x509cert']`
246 endpoints files uses the setting file of the toolkit's base folder.
259   settings.php file which contains the basic configuration info of the toolkit.
261   advanced_settings.php file which contains extra configuration info related to
263 * `_toolkit_loader.php` - This file load the toolkit libraries (The SAML2 lib).
264 * `compatibility` - Import that file to make compatible your old code with the
288  * Use a `settings.php` file that we should locate at the base folder of the
294 There is a template file, `settings_example.php`, so you can make a copy of this
295 file, rename and edit it.
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
624 file located on the base folder of the toolkit. You can load this file in this
638 you will need to load the `compatibility.php`, file which loads the SAML library files,
669 …`endpoints/acs.php`), then the ACS endpoint will redirect the user to the file that launched the S…
671 We can set a `'returnTo'` url to change the workflow and redirect the user to the other PHP file.
706 This code will provide the XML metadata file of our SP, based on the info that we provided in the s…
1032 endpoint will redirect the user to the file that launched the SLO request.
1035 to other php file.
1084 We can code a unique file that initiates the SSO process, handle the response, get the attributes, …
1413    the different folders and Loads settings info from settings file or
1522  * Use a `settings.php` file that we should locate at the base folder of the
1531 If you check the code of the index.php file you will see that the `settings.php`
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
1543 `metadata.php` file. Configure the IdP based on that information.
1586 Notice that all the SAML Requests and Responses are handled by a unique file,
1587 the `index.php` file and how `GET` parameters are used to know the action that
1597  * Use a `settings.php` file that we should locate at the base folder of the
1601 The first is the case of the demo2 app. The `setting.php` file and the
1602 `setting_extended.php` file should be defined at the base folder of the toolkit.
1613 `metadata.php` file. Based on that info, configure the IdP.
1619 unique file, the `index.php` file. This demo1 uses high-level programming.
1673 You will find an `example_settings.php` file at the demo-old's folder that
1674 could be used as a template for your `settings.php` file.
1686 `metadata.php` file. After that, configure the IdP based on that information.
1693 The `index.php` file acts as an initiater for the SAML conversation if it should