DragonBe

#Lowlands PHP community

This is a list of all PHP communities in Belgium, the Netherlands and Luxembourg

• PHPBenelux

Netherlands (14)

• Groningen
• GroningenPHP

DragonBe

<?php
declare(strict_types=1);

use League\OAuth2\Client\Provider\GenericProvider;
use Microsoft\Graph\Graph;
use Microsoft\Graph\Model;

const APP_SESS_ID = 'AZPHPSID';

const OAUTH_APP_ID             = '';

DragonBe

<?php
declare(strict_types=1);

namespace Dragonbe\Utility;

use Exception;

/**
 * This class provides two-way encryption and decryption
 * possibilities to store sensitive data or personal

DragonBe

I posted several talks about compiling PHP from source, but everyone was trying to convince me that a package manager like Homebrew was a more convenient way to install.

The purpose of Homebrew is simple: a package manager for macOS that will allow you to set up and install common packages easily and allows you to update frequently using simple commands.

I used a clean installation of macOS Sierra to ensure all steps could be recorded and tested. In most cases you already have done work on your Mac, so chances are you can skip a few steps in this tutorial.

Apache and PHP with homebrew

I’ve made this according to the installation instructions given on GetGrav.

DragonBe

# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = '2'

@script = <<SCRIPT
# Fix for https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1561250
if ! grep -q "ubuntu-xenial" /etc/hosts; then
    echo "127.0.0.1 ubuntu-xenial" >> /etc/hosts
fi

DragonBe

The assignment (max 1h30): Salary Payment Date tool

This assignment gives us a good understanding about the thought-process and the capabilities of the developer. This doesn’t have to be a rock-solid, highly scalable super fancy production-ready application, but just something that allows us to get an idea of the developer's skills and level.

Try to keep things simple. If frameworks, libraries or databases are needed to write the application, please mention them and the arguments why they were required in the documentation for this assignment.

NOTE: This is a sample code and will only be used for evaluation purposes

Requirements:

DragonBe

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.require_version ">= 2.2.0"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vagrant.plugins = ["vagrant-vbguest"]

DragonBe

<?php
declare(strict_types=1);

ini_set('highlight.comment', '#cc8800');
ini_set('highlight.default', '#6699cc');
ini_set('highlight.html','#000000');
ini_set('highlight.keyword', '#993333');
ini_set('highlight.string', '#66cc66');

$sourceCode = $previewCode = '';

DragonBe

Auth Stnadard Requirements

Problem statement

To tackle the common application pattern for authenticating, registering, resetting credentials, verifying, and unregistering from an application, the common patterns exists but many implementations make it hard to use the best solutions of different frameworks. While almost each application has this requirement, no standard has been defined.

Possible reasons why it's difficult

• Too many backend solutions for storing and updating credentials (DB, LDAP/AD, API, SSO, SAML, …)
• Added complexity when authorisation is required
• Added complexity when MFA is required

DragonBe

<?php
namespace FinalClass;

require_once __DIR__ . '/vendor/autoload.php';

use PHPUnit\Framework\TestCase;

final class Foo
{
    protected $bar;