Introduction

This component has been designed as an endpoint for performing both authentication and authorisation operations in a transparent way for the requester.

Configuration files

Before launching the project, it's necessary to review:

• app_configuration.json file. This file contains keystore and truststore files configuration. Required to SSL certificates.

   cd projectPath / configuration_files  / config
   vi app_configuration.json

• configuration.json file. This a second file which contains keystore and truststore files configuration. Required to SSL certificates.

   cd projectPath / configuration_files / config
   vi configuration.json

• network_configuration.json file. This file contains the endpoints that Security Facade requires PEP-Proxy, XACML-PDP, IdM-Keyrock and itself.

   cd projectPath / configuration_files  / config
   vi network_configuration.json

NOTE: You must be sure that corresponding keystore and truststore files are included in projectPath / configuration_files / certs folder.

Configuration docker-compose.yml file

There isn't any additional required configuration in this file.

Optionally, only for testing environments, you can disable using disable_certs variable the SSL certificates validation from Security Facade component to IdM-Keyrock one.

Prerequisites

To run this project is neccessary to install the docker-compose tool.

https://docs.docker.com/compose/install/

Launch then next components:

• XACML-PDP component running.
• IdM-Keyrock component running.

Installation / Execution.

After the review of network_configuration.json file and docker-compose file, we are going to obtain then Docker image. To do this, you have to build a local one, thus:

cd projectPath / security-facade
./build.sh

The build.sh file contains docker build -t iotcrawler/securityfacade ./ command.

Finally, to launch the connector image, we use the next command:

cd projectPath / security-facade
docker-compose up -d

Monitoring.

• To test if the container is running:

docker ps -as

The system must return that the status of the Security Facade container is up.

• To show container logs.

docker-compose logs securityfacade

Security Facade functionality.

Security Facade is waiting a POST request with an specific format data body.

curl --location --request POST 'https://<Facade-IP>:<Facade-Port>/CapabilityManagerServlet/IdemixTokenIdentity' \
	 --header 'action: <action>' \
	 --header 'resource: <resource>' \
	 --header 'device: <device>' \
	 --header 'idemixIdentity: {"name": "<IdM-user>","password": "<IdM-password>"}'

• idemixIdentity: IdM user credentials (IdM-user and IdM-password).
• device: endpoint of the resource’s request (protocol+IP+PORT).
• action: method of the resource’s request ("POST", "GET", "PATCH"...).
• resource: path of the resource request.

License

Security Facade Project source code files are made avaialable under the Apache License, Version 2.0 (Apache-2.0), located into the LICENSE file.