# Vision Project - Using Idp Authentication

**URL:** <https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [May 2, 2024, 2:55pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831 "2024-05-02T14:55:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Newbie10](https://avatars.discourse-cdn.com/v4/letter/n/a698b9/32.png) [@Newbie10](https://forum.inductiveautomation.com/u/Newbie10)\
**Post date:** [May 2, 2024, 2:55pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/1 "2024-05-02T14:55:31Z")

</div>

We are wanting to use Badges to track and make certain edits, so we would have to use idp authentication, but we are also looking to do an auto login for lower level edits. We only know of the "switchUser()" that only works with classic auth.

Is there any way to have a "default" account login via idp, or is this only doable with the classic authentication?

Open to other suggestions, if any..

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 2, 2024, 3:05pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/2 "2024-05-02T15:05:13Z")

</div>

What mechanism are you using for the badge scans? In Vision, if you can configure that as a serial device, you can monitor it in the background, then handle the badge via script (leading to switchUser). You don't need an IdP for this.

---

<div class="post-metadata">

**Author:** ![Newbie10](https://avatars.discourse-cdn.com/v4/letter/n/a698b9/32.png) [@Newbie10](https://forum.inductiveautomation.com/u/Newbie10)\
**Post date:** [May 2, 2024, 3:09pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/3 "2024-05-02T15:09:27Z")

</div>

Ohh, that may seem promising. Definitely will have to look into this some more. You don't happen to know the resource(s)? We will use a usb badge reader (i.e rfidea reader)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 2, 2024, 3:14pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/4 "2024-05-02T15:14:34Z")

</div>

It really depends on the reader. Many USB readers can be configured to be keyboard wedges or virtual serial ports. For Vision, for best results, you want the latter.

You'd have a client background timer event check the serial port for characters a couple times per second, and when received, decipher and trigger whatever custom login function you need. Or simply store the badge info in Vision Client tags where your UI code can "see" it.

---

<div class="post-metadata">

**Author:** ![Newbie10](https://avatars.discourse-cdn.com/v4/letter/n/a698b9/32.png) [@Newbie10](https://forum.inductiveautomation.com/u/Newbie10)\
**Post date:** [May 6, 2024, 5:52pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/5 "2024-05-06T17:52:28Z")

</div>

If we did do something similar, we would still have to switch user with a valid password from the current user logging in, right?? Since the 'switchUser' function needs a password parameter.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 6, 2024, 6:17pm UTC](https://forum.inductiveautomation.com/t/vision-project-using-idp-authentication/89831/6 "2024-05-06T18:17:01Z")

</div>

Yes, unless you separate badge activity into a completely separate system (orthogonal to logged-in user).