We’ve always been keen to make it as easy as possible for you, as a developer, to get authenticated against our API. This is why we used a simple API Key model. We had feedback from some developers that they would prefer us to allow a more traditional session cookie approach to authentication.
In our most recent version of LDC Via, we’ve enabled just that. There are now two different ways that you can authenticate your users against our services. You can continue to use the API Key if that suits your need. But you can also now use a session cookie.
You get allocated the cookie quite simply. You just post the username and password of the user to our service and we return a session cookie if it is valid. Then, whenever you make another request against our services you have to pass the session cookie back to our servers. If the cookie is still valid then we will perform the operation. It’s all documented in our API page.
This is just one example of adding features to LDC Via because you, our users, want them. If you have ideas for improving LDC Via, please do contact us.
The SSL Problem and How to Deploy SHA2 Certificates
Lake Eola A*
Two years ago enabling your site with SSL was a simple affair, buy a certificate or create your own, install it, then just remember to renew it every couple of years. Then, suddenly security holes are being found in SSL virtually every month , popular browsers stop connecting to your site to protect themselves, and you’re continually being told your users data is at risk. In this session we will discuss how it all went wrong and can go wrong again, then go through each step of requesting, generating and deploying a 4096 SHA-2 certificate to use in a keyfile by Domino, IBM Connections, IBM Sametime and other WebSphere products. If you work with these IBM products and need to secure them with confidence this session will show you how!
Matt White will be presenting a quickfire session about node.js:
node.js for Domino Developers
Solution EXPO Theater*
The world of web application development is big, really big. One of the most popular platforms is node.js. XPages developers already have a leg up in understanding node.js and in this session you’ll find out the basics: how to create a basic web application. But then we’ll push it a little bit further; how to integrate an application with your Domino data. We’ll cover the best development tools and some useful tips and tricks to help on your journey to become a node.js developer.
And of course we’re keen to talk to people about LDC Via , so if you’d like to arrange a meeting you can do that here.
We busy folks at LDC Via are hosting a webinar on January 12th which will introduce you to the LDC Via tool and platform. If you want to know what this stuff is all about, and see it in action, you should sign up right away.
Julian and Matt will be presenting the webinar itself, and Ben will be “back-room boy”, responding to any questions on-line and in the webinar chat.
We hope you can join us: we have had a fair bit of interest in LDC Via over the past few months, but equally a lot of people still ask us what it is all about. This session will answer those questions, and more!
We’ve spoken before about LDC Via Lens, but some things bear re-visiting, especially when the LDC Via pixies have been hard at work delivering new features that will put a smile on any developer’s face!
Today, we want to talk to you about “virtual fields”, a relatively new addition to LDC Via Lens. Anyone with a Domino background will be comfortable with the concept of virtual fields: essentially they a modern version of computed-for-display fields in IBM Lotus Notes & Domino applications.
A virtual field forms part of a collection schema, and can be referenced both from an API call and from any user interfaces you use with your migrated data—either within the LDC Via Lens application itself, or your own custom UI.
If you want to see how virtual fields work, and how simple they are to implement, check out our recent video on LDC Via Lens (virtual fields are covered around one minute in, but you should most definitely watch the whole thing).