Recently I had to put together an API call which needed to be authenticated by an application that we are building inside of an Electron Packager. Instead of using a session based implementation, I looked into using JSON Web Token so we could make the calls without having to open up a unnecessary session on the server. I did look at using Basic Auth inside of Laravel but I felt that JWT seemed to offer a bit more security as the calling application would need to have a valid token in order to make subsequent calls to the server.JWT allows for a stateless authentication exchange between the application and the server by taking a username or email and a password and then passing back to the application a token generated by a key and with a date of expiry. Because our API was built on Laravel we were able to do this easily using JWT-Auth.Firstly, add the JWT-Auth package to your composer.json file:
Posted on February 04, 2016
When working with videos it is sometimes preferable and cost effective to utilise a service such as YouTube to serve them to users that visit your website. Recently we had to use YouTube videos that need to be updated on a button click for a project which users could vote for their favourite video.
Posted on September 08, 2015
Posted on May 18, 2015
My first experience with Pixel & Tonic came with their use of plugins for the popular CMS solution Expression Engine. I used this to build and oversee applications for a number of touch screens running in a tourist space in California. This included the use of their Assets plugin, Field Pack and Matrix plugin.
Posted on May 07, 2015
Every now and again we put together a Facebook tab to promote various campaigns across various countries around the world. With the introduction of Facebook's business manager we are starting to properly localise our applications so we can use one application that handles multiple localisations with one Facebook developer application. Facebook passes two pieces of data via its signed request that we can use to achieve this. The country that the page is being viewed from and the users language that they select with they initially sign up. This provides us with enough information to appropriately display content based on their region. When we localise tab applications we normally use an XML document to hold all the content on the page and links to images etc... This allows us to pass on the XML document to people in the office so that it can be populated with the locale content accordingly. Obviously this can be achieved in other ways such as localised through a PHP page or different localised database tables.
Posted on March 26, 2015