ADC

Use Case: Limiting the Number of Sessions

December 10, 2024

Contributed by:

C C S

In this use case, the requirement is to limit the number of active backend sessions. In the deployment, each session login has login in the URL and each session logout has logout in the URL. On successful login, the backend sets a sessionid cookie with a unique 10 character value.

To achieve this use case, perform the following operations:

Create a map variable that can store each active session. The key of the map is the sessionid. The expiry time for the variable is set to 600 seconds (10 minutes).
```
> add ns variable session_map -type map(text(10),ulong,100) -expires 600

```
Create the following assignments for the map variable:
- Create an entry for the sessionid and set that value to 1 (this value is not actually used).
```
 > add ns assignment add_session -variable '$session_map[http.req.cookie.value("sessionid")]' -set 1
 
```
- Deallocate the entry for a session ID, which implicitly decrements the value count for session_map.
```
 > add ns assignment delete_session -variable '$session_map[http.req.cookie.value("sessionid")]' -clear
 
```
Create responder policies for the following:
- To check if a map entry exists for that sessionid in the HTTP request. The add_session assignment is executed if the map entry does not exist.
```
 > add responder policy add_session_pol 'http.req.url.contains("example") || $session_map.valueExists(http.req.cookie.value("abc"))' add_session
 
```
  Note: The valueExists() function in the add_session_pol policy counts as a reference to the session’s map entry, so each request resets the expiration timeout for its session. If no requests for a session are received after 10 minutes, the session’s entry will be deallocated.
- To check when the session is logged out. The delete_session assignment is executed.
```
 add responder policy delete_session_pol "http.req.url.contains(\"Logout\")" delete_session
 
```
- To check for login requests and if the number of active sessions exceed 100. If these conditions are satisfied, in order to limit the number of sessions, the user is redirected to a page that indicates that the server is busy.
```
 add responder action redirect_too_busy redirect "\"/too_busy.html\""
 add responder policy check_login_pol "http.req.url.contains(\"example\") && $session_map.valueCount > 100" redirect_too_busy
 
```

Bind the responder policies globally.

bind responder global add_session_pol 30 next
bind responder global delete_session_pol 10
bind responder global check_login_pol 20
<!--NeedCopy-->

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Use Case: Limiting the Number of Sessions

December 10, 2024

Contributed by:

C C S

December 10, 2024

Contributed by:

C C S

Use Case: Limiting the Number of Sessions

In this article