Digital Impact Radio has been a growing podcast where we’ve been talking to different people in the industry about technology and the impacts upon themselves, their businesses and the industry at large. Currently, it’s been something that’s been driven through our own networks and Oracle people interviewing others that we meet.
Read More Here to read what changes we’re making to bring more stories to you.
I’ve recently updated my twitter and medium descriptions.
It takes a village to grow. Community, friends and family are important to me.
I’ve written about it in a recent article hosted on medium titled It takes a village … I talk about what it means and what I’m trying to do. And it will take a village. If you are interested, contact me and let’s do this together.
I’m starting a series of blogs and collective content around “not just the tech”. This is where the inspiration has come from and a general observation:
Continue reading “It’s not always about the Tech …”
How to use the Bosch XDK with the Oracle IoT cloud service.
As I continue to work with various IoT vendors to see how they could be used with the Oracle IoT cloud service, I came across one of these nice little Bosch XDK kits.
This is a demo kit to show off the many Bosch sensors available and give people an environment for prototyping. Here are some of the built-in sensors:
The device has built-in wifi and Bluetooth LE.
My goal was to get this to periodically send sensor data into the IoT cloud service and make it easy for others to do the same.
Continue reading “Oracle IoT – Working with Bosch Devices”
Previously in this series we have examined what is required on an Access Management side in order to support a micro-services architecture, providing services for authentication, user management, assurance, etc. In this post, we expand the scope, looking at how to enable new services to easily implement access and authorisation appropriately, as well as a discussion about how they can authenticate to each other. Ultimately the creation of a secure system involves security of all parts, not just the access management services which facilitate it, and so this post focuses upon working towards enabling that. Security is also built upon organisational culture, and while it is a little difficult to instil that through a blog post, taking steps to create a technical foundation which allows the Access Management teams to be open and collaborative instead of being the team that says ‘no’ is unlikely hinder such cultural development.
Continue reading “Access Management and Micro-services – Part 4: Enabling Other Teams and Inter-Service Authentication”
Continuing from the previous post which dealt with the core concepts around performing authentication and authorisation in a distributed environment, this post expands upon those concepts, looking at additional factors for authorisation decisions, including supplementary information, authentication challenges and risk assessment. While basic authentication and authorisation requirements can be met through the use of JWTs and OAuth, this post shifts to tackling bespoke requirements, outlining potential services which could provide capabilities above and beyond what is captured in those standards.
Continue reading “Access Management and Micro-services – Part 3: Advanced Authorisation and Assurance”
In my previous post in this series I covered linking GitHub and DockerHub and configuring the environment such that a build of a Docker image was triggered on updates to GitHub. In this final post of the series I will take you through the steps to pull the image from Docker Hub into OCCS in order to run the application. It should be noted that the image built on Docker Hub in my example is only the web tier that contains my Node.js project (APIs and SwaggerUI). The MongoDB component of my OCCS Stack is pulled directly from Docker Hub when my Stack containing the Web Tier and Database Tier services is deployed to OCCS. Continue reading “Exploring GitHub Docker Hub and OCCS Part 4”