#ICYMI: A recent decision by the Australia Fair Work Commission has confirmed that employers are entitled to reject employees’ medical certificates when they are too vague to enable the proper discharge of basic legal obligations. https://goo.gl/YKKd6F
UK: What Might Brexit Mean for Employment Law and Access to Skills?
#ICYMI: Continued access to a pool of people with the right skills and experience is the single biggest HR concern for U.K. businesses preparing for Brexit. Employers are also concerned to know the impact of Brexit on the employment law regime in the U.K. https://goo.gl/fxvwGJ
Allowing Users to Get Their Own OAuth Tokens for Accessing an API
#ICYDK: I run a lot of different applications that depend on GitHub and that use GitHub authentication as the identity and access management layer for these apps. One of the things I like the most about GitHub and how I feel it handles it’s OAuth more thoroughly than most other platforms is how they let you get your own OAuth token under your settings > developer settings > personal access tokens. You don’t need to set up an application and do the whole OAuth dance, you just get a token that you can use to pass along with each API call.
I operate my own OAuth server, which allows me to authenticate using OAuth with many leading APIs, so generating an OAuth token and setting up a new provider isn’t too hard. However, it is always much easier to go under my account settings, create a new personal access token for a specific purpose, and get to work playing with an API. I wish that ALL API providers did this. At first glance, it looks like GitLab, Harvest, TypeForm, and ContentFul all provide personal access tokens as a first option for on-boarding with their APIs. Demonstrating this is more of a pattern than just a GitHub feature. https://goo.gl/gnCd75 #DataIntegration #ML
