# 3: Assigning HTTPS requests to a user/finger

**URL:** https://developer.ekey.net/t/3-assigning-https-requests-to-a-user-finger/29
**Category:** HTTPS requests
**Created:** [June 20, 2022, 2:38pm UTC](https://developer.ekey.net/t/3-assigning-https-requests-to-a-user-finger/29 "2022-06-20T14:38:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![productmanagement](https://dub1.discourse-cdn.com/flex017/user_avatar/developer.ekey.net/productmanagement/32/53_2.png) [@productmanagement](https://developer.ekey.net/u/productmanagement)
#### Post date: [June 20, 2022, 2:38pm UTC](https://developer.ekey.net/t/3-assigning-https-requests-to-a-user-finger/29/1 "2022-06-20T14:38:04Z")

</div>

# Assigning HTTPS requests to a user/finger

If you want to configure a finger to execute an HTTPS request, you must follow the same logic as with standard ekey bionyx functions.  
Just select the desired user, then the desired (previously stored) finger and assign the function(s) in the desired access area.

The device will trigger the configured function each time the finger matches!

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/ekey/original/1X/3cc479a78e697dd4f87c4ad03b0d5d7dee416da2.png)

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/ekey/original/1X/f59b3dd40a508ffa0a44e5d8498538934479963e.png)

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/ekey/original/1X/ca659d30755bad21127bac96012a1191f5573a01.png)

---

<div class="post-metadata">

### Author: ![productmanagement](https://dub1.discourse-cdn.com/flex017/user_avatar/developer.ekey.net/productmanagement/32/53_2.png) [@productmanagement](https://developer.ekey.net/u/productmanagement)
#### Post date: [February 9, 2023, 9:23am UTC](https://developer.ekey.net/t/3-assigning-https-requests-to-a-user-finger/29/2 "2023-02-09T09:23:14Z")

</div>