How to Control iBroadlink RM Mini 3 from RASPBERRY PI or Ubuntu 16.04 LTS

A few days ago I bought an iBroadlink RM mini 3, it is a cheap IR Control that you can use to send IR Signal from a WIFI network. You can control a lot of IR equipment as TVs, STBs, ar-conditioning, heaters and others.


This product has software for iOS and Android, it is amazing for dummy users. But it enables a connection from your local network to a chinese site. I don’t like this kind of solution that is invasive, but is easy for the customers.

I’ve an old RPI mobel B+, 512mb RAM working with Raspbian Jessy and I started learning how to control my RM mini 3 by a command line. I found some good projects in Github which I’ve used as base for my project.

I took the project Python Broadlink as base and as the result I wrote the following script named If you prefer you can execute line by line, the results are the same.

sudo su
cd /home/pi
mkdir rm3
cd rm3
apt-get update
apt-get -y install python-dev
apt -y install python-pip
apt-get -y install git
git clone
cd python-broadlink/
python -m pip install pycrypto
python -m pip install netaddr
python install

After a successful installation I got my RM mini 3 working, just using the command in the rm3/python-broadlink/cli folder :


This command returned the following information:


The following command line was used to send commands to the RM mini 3:

./broadlink_cli --type 0x2712 --host --mac aabbccddeeff

First test, get response from RM mini 3, in this case get the temperature:

broadlink_cli --type 0x2712 --host --mac aabbccddeeff --temp

And the result was:


It is working! Let’s go to the next step:  Create a file with codes from a TV remote control. Let’s use the RM mini 3 to get the codes and save it in a file.

a) Execute the following command:

./broadlink_cli --type 0x2712 --host --mac aabbccddeeff --learnfile OFFICE-TV.power

At this moment the led is in white color.

b) Point you TV Remote Control to RM mini 3 anc press power.


Led is off now and file created. Success!

Now I can use it to turn on and turn off my TV, see the command below:

./broadlink_cli --type 0x2712 --host --mac aabbccddeeff --send @OFFICE-TV.power

I did the same procedure for other TV Remote Control buttons as volume up, volume down, source and others. Everything works.

Enjoy it.




How to Manually Configure VMWARE Networking on Linux Command Line

I few days ago I’ve started a new benchmark of VMWARE Server running on Linux no GUI (text only). Unfortunately there is no good documents regarding the manual networking configuration for VMWARE Workstation 12.5.5, therefore I’ve decided explain a little bit.

I’m using a UBUNTU 16.04.2 server LTS, only text and found a situation when I’ve started a network configuration for 2 NICs. Until now I’ve used the VMware network configation tool to setup the network, but I cant do it anymore, there is only text mode available. Of course it was my first time configuring VMWare on text mode and I spend some time to understand.

The VMWare networking configuration is stored in the following folder on Ubuntu:


There are some files related to the configuration and two of them are related to the network:

  • netmap.conf
  • networking

Both are necessary to configure the network.

My system has 2 NICs and I want to set them as bridge.

First of all, stop vmware services typing the following command.

sudo vmware-networks –stop

Change the file networking.

sudo nano /etc/vmware/networking

When your system is new, probably you will find something like the configuration below:

answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH A0A27BDE00F200EC8A8A33C78C2FE470F70B5913
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH BD4BA5BF4519EA76ADECC761036E849493361616
answer VNET_8_NAT yes

Lets add new NICs as Bridge

add_bridge_mapping enp2s0 0
add_bridge_mapping enp5s0 2

The line add_bridge_mapping enp2s0 0 will define a custom bridge for vmnet 0, see below:

enp2s0 = NIC, it could be eth0!
enp2s0 0 = tells to vmware use the NIC enp2s0 as bridge on vmnet0.

The second line: add_bridge_mapping enp5s0 2 

NIC enp5s0 will be a bridge for vmnet2.

Changing the /etc/vmware/netmap.conf

nano /etc/vmware/netmap.conf = “Bridged”
network0.device = “vmnet0” = “HostOnly”
network1.device = “vmnet1” = “VMNet2”
network2.device = “vmnet2” = “NAT”
network8.device = “vmnet8”

Change or add only the bold lines.

It’s time to test, therefore start  vmware network services.

sudo vmware-networks –start


You can use the command  vmware-networks –status in order to check the network status, see the example below:


Good luck!


How to Configure MS ADFS 3.0 as Identity Provider for SAP HANA Cloud Platform

This post is a step-by-step configuration guide and it will help you to understand the steps and specifics to configure MS ADFS 3.0 (Microsoft Active Directory 3.0) as Identity Provider (IdP) for SAP HANA Cloud Platform (SAP HCP).
In this post, you see how to enable the MS ADFS 3.0 as IdP for your applications in SAP HCP.

1. How it Works

By default, SAP HCP uses SAP ID Service as identity provider based on SAML 2.0. In addition, SAP HCP supports identity federation and single sign-on with external identity providers. In this case, we will the focus on MS ADFS 3.0 as external IdP for SAP HCP. It means we will configure SAP HCP to authenticate users on MS ADFS 3.0, instead of SAP ID Service. The following steps can describe the authentication process in a simple way:

a. User requests access to an application on SAP HCP thru the browser.
b. SAP HCP request user authentication on MS ADFS.
c. User authenticates on MS ADFS.
d. The user receives a redirect to SAP HCP and holds a SAML 2.0 Assertion in order to access the application.
e. User get access to the application

2. Prerequisites

Below you find a list of the prerequisites:
a. An SAP HCP account (In my case, I’m using an SAP HCP trial account).
b. SAP MS ADFS 3.0 configured and working with SAML 2.0.
c. IoT service enabled on SAP HCP. (If you don’t know how to do it, please follow this link).
Note: As you can see, the installation of MS ADFS 3.0 is not a subject of this blog.

3. Gettting Metadata File From MS ADFS 3.0

Before starting the SAP HCP configuration, I really recommend you to get the metadata XML file from MS ADFS. The metadata file contains information about certificates, URLs, algorithms and so on, which are required to configure the Federation between SAP HCP and MS ADFS.
The MS ADFS 3.0 provides an URL where you can access and download the Metadata; It has the following structure: https:///FederationMetadata/2007-06/FederationMetadata.xml, of course you need to replace the with the full-qualified name of your ADFS server.

4. SAP HCP Configuration.

4.1 Creating a Trusted Identity Provider

Let’s work! Now you have all you need to configure your SAP HCP to work with MS ADFS as IdP, therefore follow the instructions below:
a) Go to SAP HCP Cockpit.
b) On the menu, click on “Trust”.
c) Click on folder “Trusted Identity Provider”.
d) Click on link “Add Trusted Identity Provider”.

It’s time to import the Metadata file from MS ADFS on SAP HCP. In the folder “General”, click on Button “Browse” and import the FederationMetadata.xml file. The fields will be automatically populated with the data from the metadata file, but you need to fix some fields, see the instructions below:
a) Setup Assertion Consumer Service from Application Root to Assertion Consumer Service
b) Change the SSO URL to https:///adfs/ls/idpinitiatedsignon.aspx?logintoRP=


SAP HCP Account User: p1942090147

c) Change the Signature algorithm from SHA-1 to SHA-256
d) Leave the option “Only for IDP-Initiated SSO” unchecked.

4.2 Rebuilding the Local Provider Configuration

The local provider needs to be recreated in a custom way. In other words, you need to rebuild the local provider in order to get the metadata file from SAP HCP.
In this case, we will perform a simple rebuild of the local provider. Follow the instructions below:
a) In the Menu “Trust”, click on folder “Local Service Provider”
b) Click on button “Edit”

Follow the instructions below in order to setup a new local provider:
a) Change configuration type to “CUSTOM”
b) Fill the “Local Provider Name” with a URL based on the following rule:
c) Click on button “Generate Key Pair” in order to create new keys for signing and the certificate.
d) Enable Principal Propagation
e) Disable the option “Force Authentication”

4.3 Getting Metadata File from SAP HCP

Once you have created a custom configuration for a local provider then you can perform this step.
An option to get the Metadata file will be available after you save the custom configuration for “Local Service Provider”. Therefore, click on link “Get Metadata” and save the file.

4.3 Create a Relying Party Trust 

Creating a relaying party trust on MS ADFS 3.0 is easy, but you need to pay attention for each step presented here.

a) Open MS ADFS Management and expand three menu up to “Relying Party Trusts”.
b) Click on “Add Relying Party Trust”

Configure a new Relying Party Trust in thirty clicks on fourteen screenshots;

1) Click on next
2) Select “Import data about the relying party from a file”. Do you remember the Metadata file you save? You need it now.
3) Click on “Browse” and select the Metadata file you saved.
4) Click on Next.
5) Give a name, for example SAP HCP
6) Enter a description.
7) Click on Next.
8) Select “I don’t want to configure multi-factor authentication setting for this relying party trust at this time”.
9) Click on “Next”.
10) Select “Permit all users to access this relying party trust”.
11) Click on button “Next”
12) Just perform a click on “Next”
13) Check the box “Open the Edit Claim Rules dialog for this relying party trust when the wizard closes”
14) Click on “Add Rule”.
15) Select “Send LDAP Attributes as Claims” for Claim Rule Template.
16) Click on Next.
17) Give a name for the rule, in this case I gave “R1”.
18) Choose Active Directory for Attribute store option.
19) Mapping Attribute: “SAM-ACCOUNT-NAME” to “Given Name”
20) Click on Next.
21) Click on “Add Rule”.
22) Select “Transform Incoming Claim” for for Claim Rule Template.
23) Give a name for the rule, in this case I gave “R2”.

24) Choose “Given Name” for Incoming Claim Type.
25) Choose “Name ID” for Outgoing Claim Type.
26) Choose “Unspecified” for Outgoing Name ID format
27) Select: Pass through all claim values
28) Click on “Next”.
29) Click on “Apply”
30) Click on “Ok”

Done! Just close ADFS Management.

4.5 Mapping Users 

At this point we will create a mapping for all users, the users exists only in MS ADFS. You don’t need to create users in SAP HCP, but you need to create groups to give access to your Applications. In this case, we will create a group and link it to IdP (MS ADFS).

4.5.1 Create a Group

Go back to SAP HANA Cloud Platform Cockpit and perform the following activities:

a) Click on “Authorizations” in the right side of the screen.
b) Click on folder “Groups”.
c) Click on “New Group”.

d) Give a name to the group. In my case I used “demo-sso”.
e) Give the following role to the group “demo-sso!.

Note: Do not forget to click on button “Save”.

4.5.2. Mapping Group to IdP

Perform the following tasks:

a) On the SAP HANA Cloud Cockpit, click on menu “Trust”.

b) Click on folder “Trusted Identiity Provider”.

c) Click on IdP name.

d) Click on folder “Groups”.

e) Select the group you’ve created.

f) Click on “Save”.

You can create access for specific group, for example, you can combine groups and permission and map these groups adding assertion-based group. But it is a subject for another blog.

At this time, the users can access the IoT Cockpit with SAML 2.0.

4.5.3 Test

a) Ensure that IoT Cockpit is activate in your instance.
b) Ensure that you got the URL for Iot Cockpit of your instance.
c) Open the browser in a private mode. It is just to confirm that a identity will be required.
d) Activate the developer tools; Press F12 in Google Chrome and click on Network and check the Preserve Log box.
e) Enter the link of the IoT Cockpit, see the example:

Lets understand, see my screenshot below:

The user is “simpson” (SAM-Account name on Active Directory).

Following the Browser’s sequence:

  • User open his browser and put the IoT URL.
  • User’s browser receives an redirect the user to MS ADFS login URL.
  • The user is logged on Windows Network and has a Kerberos ticket, therefore the user gets a SAML 2.0 assertion from MS ADFS and User’s browser moves to SAP HCP Authentication endpoint.
  • User authenticates on SAP HCP with their SAML 2.0 Assertion and receives an redirect to the IoT Cockpit.

Remember: you do not need to create the users on HCP, you just need to create groups and give the access.

See you on next blog.

How to install SAP OpenUI5 on RASPBERRY PI

A few days ago I was checking my old hardware and I found a RASPBERRY PI (RPI) version 1 model B. It’s a very small computer module and this amazing hardware has two USB ports, 512MB of SDRAM, one Fast Ethernet (100 mpb/s), one HDMI, one RCA and a audio jack. In addition RPI requires an SD card to work as hard disk. It also has a small form factor measuring 65mm in length, it’s small as credit card and it works with a 5V/1.5A power supply. The processor is an ARM1176JZF-S with 700 MHz clock.


There are some operational systems available for this version of RPI, but I choose a version based in Debian called Raspbian, it is optimized for the Raspberry Pi hardware and  it is supported by Raspberry PI Foundation.

I was learning about SAP Fiori frontend, as well as, I was developing an internal site at home in order to support some activities that I judge important for me. For example, sometimes I need to wake up some machine, monitor the surveillance cams and get alerts from nobreaks. Therefore I chose SAPUI5, because I could learn and enjoy my RPI at same time.

Recently I’ve started thinking about Internet of Things (IoT) and how to implement it at home. I’ve realized that Raspberry is a good choice for that kind of development, especially after the last announced version of RPI, the RASPBERRY PI ZERO, it’s smallest than RASPBERRY PI versions 1 and 2, and it’s cheapest than both.

Raspberry PI ZERO made in Wales and priced at just $5

Raspberry PI ZERO Feautures:

  • 1Ghz, Single-core CPU
  • 512MB RAM
  • Mini HDMI and USB On-The-Go ports
  • Micro USB power
  • HAT-compatible 40-pin header
  • Composite video and reset headers

    RPI Zero size

Lets take a look how to configure RPI to run OpenUI5 with Debian Jessie. If you are planning to use the Debian Wheezy keep in your mind that the configuration is a little bit different and probably you’ll experience some troubles.

  1. Preparation
    Take a look here in order to install the RPI with Raspbian, it’s very simple and you can do it on Windows, Mac or Linux. Of course you need a SD Card.
    The steps for configuration described below are for Debian Jessie and you can experience some troubles if you are trying to configure with Debian Wheezy installed on RPI.
  2. Install and Apache Web Server
    After you have installed your RPI, install the Apache Web Server. Do not forget, your RPI must be connect to the Internet by Cable or WI-FI.On the terminal type the following command:

    sudo apt-get install apache2 -y
    service apache2 restart

    Test your apache typing the url on the browser http://<RPI IP>. Example, if the RPI is running on IP, type

    You should see something like this:


  3. Deploy OpenUI5 on RPI
    The root document configured for APACHE 2.4 is /var/www/html/Go to the web root and create the folder /ui5.Terminal commands:

    cd /var/www/html
    mkdir /var/www/html/ui5
    cd ui5

    Download the OpenUI5 sdk package

    sudo wget

    Unzip the package:

     sudo unzip
  4. Teste you environment

Go to browser and type the following URL http://<RPI IP>/ui5 in order to test your Openui5 SDK. Do not forget to REPLACE the <RPI IP>.


You must see a screen like this:



It is simple, isn’t it?

If you don’t have a RPI yet, you can test my configuration at

The same configuration can be applied for Ubuntu 14.04 with Apache 2.4.

Configuring MS ADFS 3.0 as Identity Provider for SuccesFactors

Many companies are using MS ADFS 3.0 as Identity Provider (IdP) to authenticate users with SAML2 protocol and all of them are enabled to use ADFS with SuccessFactors (SFSF) too. Also many companies prefer to keep their users managed in the Corporate Network instead of managing users in the cloud services.

This post will show you how it’s easy to configure ADFS to work with SuccessFactors.


Due to the nature of the integration between two or more systems, it’s necessary some explanation about the tasks and responsibilities. The table below is a responsibility matrix, keep in your mind that’s a basic suggestion and the idea is to identify the tasks of each team or person.




1. Configure MS AD FS.

  • Check ADFS availability
  • Validate Infrastructure
  • Provide access from Corporate Network to SuccessFactors Cloud Services


2. Deliver the forms.

  • SAP/SuccessFactors Consultant must request information, certificate and others, thru the form.


3 Fill out the forms

  • The forms must be filled and returned to SAP/SuccessFactors.


4. Cloud Configuration

  • Configure SSO environment as requested in the form


5. Test SSO

  • Provide authentication tests for SSO with SMAL 2.0



  • After the tests the customer team must confirm the architecture and the results.


Keep in your mind that we are considering that MS ADFS is working and do not forget, the MS ADFS must be allowed to handle Web SSO tokens with SAML 2.0. The installation of MS ADFS will not be showed in this post.

Step 1 – MS ADFS 3.0 Version and Patches

I really recommend you to check on the Microsoft site if there are patches to be applied in your environment.

Step 2 – Metadata and certificates from SAP/SuccessFactors

In order to configure the MS ADFS you need to request some files from SuccessFactors. These files will provide a metadata and certificates to be used in ADFS.

Also you need to send the metatada from  ADFS to SuccessFactors. It’s quite simple, just open your browser and use the following URL https://<SERVER>/FederationMetadata/2007-06/FederationMetadata.xml. Do not forget to repalce  <SERVER> with your server address.

Export certificates used by ADFS to communicate, sign and encrpyt is not mandatory, but you can save some time doing it. To export them, open your ADFS Management from Server Manager and follow the sequence below:



2.1 In the left side of the ADFS Management has a tree view, click on Service node.


2.2 Go to Certificates, all certificates will appear in the right side of the ADFS Management.


2.3 Perform and right click on the commnication certificate and choose “view certificate”.



2.3 In a new window select the folder “Details” and click on button labeled as “Copy to File…”


2.4 In the certificate export wizard window click on “Next” button.


2.5 Select the option “No, do not export the private key” in order to export only the Public key. Click on “Next” button.


2.6 Select BASE-64 encoded X.509 in order to export the certificate as BASE64. Click on “Next” button.


2.7 Select the path and the file name which will be created.


2.8 Communication Certificate was exported, click on “Finish” button.


2.9 Repeat the process for Encryption and Signature certificates, do not forget to give a unique file name for each certificate.




2.10 Open the file saved for communication certificate and go to Certification Path.



2.11 In order to avoid missing of information,CA Root in certification path can be exported too. Perform a double click on CA Root.



Execute the same procedure have you done to export others certificates.




These files will be sent to SAP/SFSF together with the metadata xml file.

Step 3 – Configure MS ADFS

3.1 Open ADFS Management (Start the ADFS Management in the server) and start the wizard to add a Relying Party Trust for SFSF Cloud Service


3.2 Select option “Import data about the relying party from a file”


3.3 Add the configuration from Metadata.xml file


3.4 Specify the display name of the Claim


3.5 Check the option “Permit all user to access this relying party”


3.6  Confirm the certificate for Encryption




3.7 Flag this option in order to configure the Claim Rules


3.8 Click on “Add Rule” button to create new rules. Two new rules must be configured in Claim Rules


3.9 The new rule is related to LDAP attributes; Therefore choose “Send LDAP Attributes as Claims” and click on “Next”

3.10 Define the rule name as you want, choose Active Directory in the attribute store. In the mapping select SAM-Account-Name for LDAP Attribute and choose Given Name for Outgoing Claim. Click on the “Finish” button.

3.11 Create another rule


3.12 Choose the option “Transform an Incoming Claim” and click on “Next”


3.13 Give some name for the rule. Incoming type is “Given Name” and outgoing type is “Name ID”. Outgoing name ID forma must be “Unspecified”. Finish this configuration


3.14 Close this window clicking on OK button


 3.15 Close MS ADFS window and enjoy your SAML2 provider.

It will work only after the SuccessFactors has finished the configuration of their environment.

In the same way MS ADFS can be configured to provide identity for SAP NW GATEWAY and SAP PORTAL.


What’s New in SAP NetWeaver 7.5

According to SAP the SAP NetWeaver 7.5 enables technology trends like the Internet of Things (IoT), mobile, cloud, big data and analytics. The main objective is speed up the development of simple business applications.
I found some important topics which were summarized in this post. Let’s take a look into SAP NW 7.5 and see some main changes.


I think the most important point for Portal, PI/PO and BPM consultants is the Java 8 features, let’s see some security features:

  • Client-side TLS 1.2 enabled by default.
  • Stronger algorithms for password-based encryption.
  • SSL/TLS Server Name Indication (SNI) Extension support in JSSE Server.
  • The SunJCE provider is enhanced to support AES/GCM/NoPadding cipher implementation as well as GCM algorithm parameters.
  • SHA-224 Message Digests.
  • Kerberos 5 weak encryption types disabled by default.

You can see the Best Practices for NW ABAP 7.5 on my SCN BLOG Site.

Best Regards,

Alex Belle.

How to Enable SAP Fiori on NW 7.4 SP 04

I’ve prepared a simple and illustrated documentation in Portuguese about enabling SAP Fiori on NW 7.4 SP 04.

This document is a reference for a SCN Meetup Rio de Janeiro 2015 and I used to show this topic. If you are interested on SCN Meetup Rio 2015 please follow the link.

In this document I’ve explained about some steps to enable the SAP Fiori, as well as I’ve detailed the architecture of the SAP Fiori and an organized sequence of the configuration.

The following topics were touched:

  • How to download SAP Fiori Applications
  • Enable services on SICF
  • Create the SSL on STRUST
  • Enable NW Gateway 2.0 for SAP Fiori
  • Access Launchpad and Features

PDF Download: SCN-Meetup-2015-RJ-SAP-Fiori-Alex-Belle

Best Regards.

Alex Belle