OneSpan Sign Developer: Smart Cards and Callback Listeners
In this blog, I will go over what you might have missed in the OneSpan Sign Developer Community during the week of March 12th, 2018. Let's get straight to it.
OneSpan Sign offers a variety of authentication options, including support for smart cards. Specifically, OneSpan Sign supports signing with government-issued smart cards such as the Common Access Card (CAC) and Personal Identity Verification card (PIV), as well as Electronic ID smart cards and tokens issued by Trust Service Providers (TSP) in Europe. In order to have this feature enabled on your account, you will need to contact our support team.
Creating Callback Listeners
When creating an integrated solution with OneSpan Sign, you may want to use Callback Event Notifications. Essentially, when an event happens (i.e. transaction completed, attachment uploaded, etc.), a notification is sent in the form of an HTTP POST request to the registered URL in your OneSpan Sign account. The POST request contains relevant information about the event, which makes it possible for your app to act accordingly. You can choose which events you would like to receive payloads for. Only subscribing to the specific events you plan on handling is useful for limiting the number of HTTP requests to your server. You can change the list of subscribed events through the API or UI anytime. Callbacks offer many advantages. Mainly, it eliminates the need of wasteful polling. You get useful information as they happen. From the link below, you can find many examples on how to create simple callback listeners. Link to Blog If you have questions regarding this blog or anything else concerning integrating OneSpan Sign into your application, visit the Developer Community Forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn.