Biometric Authentication in Pega
Hi All,
Can anyone help me with providing some information related with Biometric authentication and Pega?
Is there any API available by which we can establish a connection between Biometric devices and Pega application?
Thanks in advance.
Tetrasoft India Private Limited
IN
Accenture
IN
Hi Dames,
Thanks for your reply. The link actually says about the basics of Biometric authentication. Also it do not suggests to implement the same in Pega.
But for me client specifically is asking about biometric authentication.
If you have any such article which explains or gives some clue about how Pega can be integrated with Biometric devices and how to read the data will be great help.
Thanks in advance
Pegasystems Inc.
IN
This is actually I am also interested to know and I cant see much material available online.
@Scott do you think you can help here ?
Accepted Solution
Pegasystems
US
Not sure how much I can add. A few comments:
Pega Mobile supports Apple Touch ID which is in essence a type of biometric-authentication.
Some customers are using biometric information to confirm the identity of a traveller.
Lastly, the lack of common standards for biometric hardware limit the capability of Pega to support biometric authentication out of the box. Or as my colleague @AndreasSittler put it:
Pega provides a few authentication types OOTB.
[1] PRPC internal (this is what you are using on your SC image) with and without SSL,
[2] container-managed (if PRPC is run inside a JEE container),
Not sure how much I can add. A few comments:
Pega Mobile supports Apple Touch ID which is in essence a type of biometric-authentication.
Some customers are using biometric information to confirm the identity of a traveller.
Lastly, the lack of common standards for biometric hardware limit the capability of Pega to support biometric authentication out of the box. Or as my colleague @AndreasSittler put it:
Pega provides a few authentication types OOTB.
[1] PRPC internal (this is what you are using on your SC image) with and without SSL,
[2] container-managed (if PRPC is run inside a JEE container),
[3] custom.
[3a] If it is custom, PRPC provides ootb-support for LDAP-based systems.
[3b] If it is custom and not LDAP (like for any SSO solution as an example), you will have to customize activities (or more) within PRPC, probably even writing a custom servlet.
Anything that involves hardware will fall into the category [3b], as it will most likely require some sort of communication with the system that connects to the hardware itself, _or_, with the hardware itself.