Monthly Archives: January 2018

First steps with UCommerce

This week I had a look at Umbraco and UCommerce. I already created a small site (just for personal practice) with Umbraco.
So I downloaded the latest versions from Umbraco (https://our.umbraco.org/download) and UCommerce (https://ucommerce.net/platform). There’s a free version of UCommerce as well.

I think UCommerce is quite interesting, because it is available for various CMS’ like Kentico, Sitecore and of course Umbraco. So I hope you can reuse your knowledge, when learning it on one platform and then you have to implement it for another project on another platform.

Just as mentioned by a colleague, there’s currently no support for specific german payment- and shipping-providers. So I’m interested in implementing them.
I already started with the payment-provider. In my case Wirecard.

My starting point for this is the documentation of UCommerce for implementing a payment-service:
https://docs.ucommerce.net/ucommerce/v7.11/payment-providers/integrating-a-payment-gateway.html

So far I found the most promising way on the wirecard page to be the “seamless checkout” page, where you first post your parameters (from the payment object, which is passed to your payment-service method above) to “Init”. You’ll get a link back then where you have to bring the user to to start the payment process.
I’m not sure, but I guess if you reached that milestone, you’ll just have to handle the payment-result in UCommerce then:
https://guides.wirecard.at/wcs:frontend_init

If anyone of you already has some more experience with Umbraco or UCommerce, I’d be glad to chat with you.

Ah – before I forget my favorite part … If you want to try this your own. I spent several hours to understand, that my biggest problem with the UCommerce Demo-Shop was the fact that I already installed the UCommerce Demo-Page … so the templates mixed up. Just do not install the Umbraco Demo-Page and everything will work fine ;-).

Coding evening and Jira API

In the first week of january, we’ve visited our colleagues in Hamburg. And when you’re driving there for some hours (and haven’t been there in a while), I couldn’t of course resist to have a nice coding-session in the evening. For that we decided even to stay a day longer, so we didn’t have to hurry to drive home when the evening got late.
Our self-set todo for that evening was to load tickets via API from a local Jira system.
So one of my colleagues took care of reading into the API and preparing the .NET classes (as well as the handling of the data), while I on the other side tried my luck with the authentication.

My mate was quite successful, in a short amount of time, because the API was documented quite well. You can retrieve boards, sprints and issues (separately and grouped by sprint) just by knowing the correct endpoints. You can find the REST documentation on the atlassian page:
https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/

But have a look at the version number. As we realized at the end of the evening: Our system was just one version below that one we needed to directly query relations between projects and boards. Patches help 😉

I myself despaired the whole evening while working on the OAuth 1.0 authentication. Actually I did that various times (whereas I have to confess that I’m not that firm in implementing such stuff), but I didn’t get that exact way on this evening.

While all my current implementations used HMAC-Sha-something as signature method, Jira insisted on having an RSA-Sha-something. No problem … i thought … if only my libraries (I tried 2 or 3) wouldn’t have acknowledged my tries to set RSA as method with the message “method not supported”.
Some days later I read into that topic again and found something like this:
https://crypto.stackexchange.com/questions/11293/hmac-sha256-vs-rsa-sha256-which-one-to-use

“While HMAC has to use a shared key between server and client (because it’s symmetric) – RSA uses only the PublicKey to validate (that’s called asymetrisch)”. So only one party has to know the privat key.
Well – ok – sounds valid. But on that evening it was already late and I didn’t get it then anymore.

And because I didn’t want to end that evening without a result, I lateron sat down in the hotel to have a further look. I already read that you could of course use the Jira API with basic authentication instead of OAuth … but there was even more (when not in a hurry to find the solution within a given time) … There is for example a library which calls itself “Atlassian SDK”. You can find it here:
https://bitbucket.org/farmas/atlassian.net-sdk/overview

My mate called it “boring” using a library – but hey – decide for yourself ;). Btw.: That library is written by a guy called “Federico Silva Armas”. LinkedIn tells us, that he’s been working at atlassian (QA engineer) and now works as core-dev on the azure-portal … well … Azure seems to be everywhere 😉

Activities during the holidays

Because Linux is a big topic in Azure as well, there’s an exam from Microsoft, that is called “Linux on Azure”. The prerequisites therefore are two things: A passed LFCS test of the Linux Foundation (Linux Foundation Certified System Administrator), as well as the MS exam 70-533 “Implementing Microsoft Azure Infrastructure Solutions”. You can find details over here:
https://www.microsoft.com/de-de/learning/mcsa-linux-azure-certification.aspx

The Linux Foundation has created a six-part series of video tutorials as a preparation for the former test. For the latter there are materials from MS. You can find both here:
http://aka.ms/azuremaster

Because I wanted to have a look at them (and had some free time) I watched them during the christmas holidays. With a monotonous enthusiams, a guy explained there in about 12h (all videos are about 1,5-2,5h long) the various topics.
It might have been a little bit more or less time – but with all my taking-notes, jumping forwards and backwards as well of course the watching, it took me about 19h.

Roughly grouped you’re told about the following topics

  • Shell
  • Folder structure (and the most important directories in Linux)
  • Filesystem + Mounting of devices
  • Editors (and especially VI)
  • Bootsequence / Bootloader / Config
  • SystemD (+systemctl)
  • Permissions (ACL,…) + Root
  • Manpages
  • Processes (pids; lists; signals)
  • Scheduling
  • Softwareinstallation + Packagemanager
  • User / Passwords / Groups
  • LSM (Linux security modules) / SELinux / PAM
  • SSH, Telnet
  • Network + Firewall (iptables) + Routing + DNS + FTP + NFS + KVM
  • Timeserver (chrony)
  • Samba
  • Mails (postfix, dovecot)
  • Apache (Webserver), Squid (Cache), MariaDB
  • Container
  • Partitions (dd, xdd, fdisk, LVM) + Raid, LUKS, Quota

So now I got a long list of dangerous superficial knowledge 😉 … I’m curious what of these I’ll learn in greater detail during this year and which I’ll need at all ;-D.