Update README.md

Author: aacotroneo

README.md

@@ -3,6 +3,44 @@ A Laravel package for Saml2 integration as a SP (service provider) based on OneL
 
 The aim of this library is to be as simple as possible. We won't mess with Laravel users, auth, session...  We prefer to limit ourselves to a concrete task. Ask the user to authenticate at the IDP and process the response. Same case for SLO requests.
 
+
+## Installation - Composer
+
+To install Saml2 as a Composer package to be used with Laravel 4, simply add this to your composer.json:
+
+```json
+"aacotroneo/laravel-saml2": "0.0.1"
+```
+
+..and run `composer update`.  Once it's installed, you can register the service provider in `app/config/app.php` in the `providers` array:
+
+```php
+'providers' => array(
+    		'Aacotroneo\Saml2\Saml2ServiceProvider',
+)
+```
+
+Then publish the config file with `php artisan config:publish aacotroneo/laravel-saml2`. This will add the file `app/config/packages/aacotroneo/laravel-saml2/saml_settings.php`. This config is handled almost directly by  [one login](https://github.com/onelogin/php-saml) so you may get further references there, but will cover here what's really necessary.
+
+### Configuration
+
+Once you publish your saml_settings.php to your own files, you need to configure your sp and IDP (remote server). The only real difference between this config and the one that OneLogin uses, is that the SP entityId, assertionConsumerService url and singleLogoutService URL are inyected by the library. They are taken from routes 'saml_metadata', 'saml_acs' and 'saml_sls' respectively.
+
+Remember that you don't need to implement those routes, but you'll need to add them to your IDP configuration. For example, if you use simplesamlphp, add the following to /metadata/sp-remote.php
+
+```php
+$metadata['http://laravel_url/saml/metadata'] = array(
+    'AssertionConsumerService' => 'http://laravel_url/saml/acs',
+    'SingleLogoutService' => 'http://laravel_url/saml/sls',
+    //the following two affect what the $Saml2user->getUserId() will return
+    'NameIDFormat' => 'urn:oasis:names:tc:SAML:2.0:nameid-format:persistent',
+    'simplesaml.nameidattribute' => 'uid' 
+);
+```
+You can check that metadata if you actually navigate to 'http://laravel_url/saml/metadata'
+
+
+
 ### Usage
 
 When you want your user to login, just call `Saml2Auth::login()`. Just remember that it does not use any session storage, so if you ask it to login it will redirect to the IDP wheather the user is logged in or not. For example, you can change the auth filter.
@@ -47,7 +85,7 @@ For case 1 call `Saml2Auth::logout();` or redirect the user to the route 'saml_l
 
 For case 2 you will only receive the event. Both cases 1 and 2 receive the same event. 
 
-```
+```php
 Event::listen('saml2.logoutRequestReceived', function()
 {
     Auth::logout();
@@ -57,42 +95,6 @@ Event::listen('saml2.logoutRequestReceived', function()
 });
 ```
 
-## Installation - Composer
-
-To install Saml2 as a Composer package to be used with Laravel 4, simply add this to your composer.json:
-
-```json
-"aacotroneo/laravel-saml2": "0.0.1"
-```
-
-..and run `composer update`.  Once it's installed, you can register the service provider in `app/config/app.php` in the `providers` array:
-
-```php
-'providers' => array(
-    		'Aacotroneo\Saml2\Saml2ServiceProvider',
-)
-```
-
-Then publish the config file with `php artisan config:publish aacotroneo/laravel-saml2`. This will add the file `app/config/packages/aacotroneo/laravel-saml2/saml_settings.php`. This config is handled almost directly by  [one login](https://github.com/onelogin/php-saml) so you may get further references there, but will cover here what's really necessary.
-
-### Configuration
-
-Once you publish your saml_settings.php to your own files, you need to configure your sp and IDP (remote server). The only real difference between this config and the one that OneLogin uses, is that the SP entityId, assertionConsumerService url and singleLogoutService URL are inyected by the library. They are taken from routes 'saml_metadata', 'saml_acs' and 'saml_sls' respectively.
-
-Remember that you don't need to implement those routes, but you'll need to add them to your IDP configuration. For example, if you use simplesamlphp, add the following to /metadata/sp-remote.php
-
-```php
-$metadata['http://laravel_url/saml/metadata'] = array(
-    'AssertionConsumerService' => 'http://laravel_url/saml/acs',
-    'SingleLogoutService' => 'http://laravel_url/saml/sls',
-    //the following two affect what the $Saml2user->getUserId() will return
-    'NameIDFormat' => 'urn:oasis:names:tc:SAML:2.0:nameid-format:persistent',
-    'simplesaml.nameidattribute' => 'uid' 
-);
-```
-You can check that metadata if you actually navigate to 'http://laravel_url/saml/metadata'
-
-
 
 That's it. Feel free to ask any questions, make PR or suggestions, or open Issues.