Increase the expiration time and update the link to the demo website

Author: habarthierry-hue

README.md

@@ -8,7 +8,7 @@
 SimpleIdServer is an open source framework enabling the support of OPENID, OAUTH2.0, SCIM2.0, UMA2.0, FAPI and CIBA. It streamlines development, configuration and deployment of custom access control servers. 
 Thanks to its modularity and extensibility, SimpleIdServer can be customized to the specific needs of your organization for authentication, authorization and more.
 
-[Website](http://simpleidserver.com), [Documentation](https://simpleidserver.com/docs/intro) and [Demo](https://website.simpleidserver.com/).
+[Website](http://simpleidserver.com), [Documentation](https://simpleidserver.com/docs/intro) and [Demo](https://website.simpleidserver.com/master/clients).
 
 ## Packages
 

tests/SimpleIdServer.IdServer.Host.Acceptance.Tests/Features/BCAuthorize.feature

@@ -3,7 +3,7 @@
 
 Scenario: Authentication response is returned with interval because PING is used
 	Given authenticate a user
-	And build expiration time and add '60' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key                       | Value                                |
 	| aud                       | https://localhost:8080               |
@@ -29,7 +29,7 @@ Scenario: Authentication response is returned with interval because PING is used
 
 Scenario: Authentication response is returned without interval because PUSH is used
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyThreeClient' and sign with the key 'keyId'
 	| Key                       | Value                                |
 	| aud                       | https://localhost:8080               |

tests/SimpleIdServer.IdServer.Host.Acceptance.Tests/Features/BCAuthorize.feature.cs

@@ -123,7 +123,7 @@ Scenario: lifetime of the request must not exceed 300 seconds (request)
 
 Scenario: request parameter must contains jti (request)
 	Given authenticate a user
-	And build expiration time and add '30' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key | Value                  |
 	| aud | https://localhost:8080 |
@@ -143,7 +143,7 @@ Scenario: request parameter must contains jti (request)
 
 Scenario: at least one token hint must be passed (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key | Value                  |
 	| aud | https://localhost:8080 |
@@ -164,7 +164,7 @@ Scenario: at least one token hint must be passed (request)
 
 Scenario: user_code is required when backchannel_user_code_parameter is true (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key           | Value                  |
 	| aud           | https://localhost:8080 |
@@ -186,7 +186,7 @@ Scenario: user_code is required when backchannel_user_code_parameter is true (re
 
 Scenario: scope or authorization_details parameter is required (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key           | Value                  |
 	| aud           | https://localhost:8080 |
@@ -209,7 +209,7 @@ Scenario: scope or authorization_details parameter is required (request)
 
 Scenario: authorization_details type is required (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key                   | Value                      |
 	| aud                   | https://localhost:8080     |
@@ -233,7 +233,7 @@ Scenario: authorization_details type is required (request)
 
 Scenario: authorization_details type must be valid (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key                   | Value                      |
 	| aud                   | https://localhost:8080     |
@@ -257,7 +257,7 @@ Scenario: authorization_details type must be valid (request)
 
 Scenario: scope must be valid (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key           | Value                  |
 	| aud           | https://localhost:8080 |
@@ -281,7 +281,7 @@ Scenario: scope must be valid (request)
 
 Scenario: client_notification_token parameter is required (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key           | Value                  |
 	| aud           | https://localhost:8080 |
@@ -305,7 +305,7 @@ Scenario: client_notification_token parameter is required (request)
 
 Scenario: client_notification_token size must be greater than 128 bits (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key                       | Value                  |
 	| aud                       | https://localhost:8080 |
@@ -330,7 +330,7 @@ Scenario: client_notification_token size must be greater than 128 bits (request)
 
 Scenario: id_token_hint must be valid (request)
 	Given authenticate a user
-	And build expiration time and add '10' seconds
+	And build expiration time and add '120' seconds
 	And build JWS request object for client 'fortyTwoClient' and sign with the key 'keyId'
 	| Key                       | Value                                |
 	| aud                       | https://localhost:8080               |