Skip to main content

A library that connects to ams using argo-ams-library and syncs with MITREid, SimpleSAMLphp and Keycloak

Project description

rciam-federation-registry-agent

RCIAM Federation Registry Agent main objective is to sync data between RCIAM Federation Registry and different identity and access management solutions, such as Keycloak, SATOSA, SimpleSAMLphp and MITREid Connect. This python library includes a module named ServiceRegistryAms/ to pull and publish messages from ARGO Messaging Service using the argo-ams-library, an API module named MitreidConnect/ to communicate with the API of the MITREid, an API module named Keycloak/ to communicate with the API of the Keycloak. The main standalone scripts that are used to deploy updates to the third party services are under bin/:

  • deployer_keycloak for Keycloak
  • deployer_mitreid for MITREid
  • deployer_ssp for SimpleSAMLphp

Installation

First install the packages from the requirements.txt file

pip install -r requirements.txt

Install rciam-federation-registry-agent

pip install rciam-federation-registry-agent

Usage

deployer_keycloak

deployer_keycloak requires the path of the config file as an argument

deployer_keycloak -c example_deployers.config.json

deployer_mitreid

deployer_mitreid requires the path of the config file as an argument

deployer_mitreid -c example_deployers.config.json

deployer_ssp

deployer_ssp requires the path of the config file as an argument

deployer_ssp -c example_deployers.config.json

Configuration

An example of the required configuration file can be found in conf/example_deployers.config.json. The different configuration options are described below.

{
  "keycloak": {
    "ams": {
      "host": "example.host.com",
      "project": "ams-project-name-keycloak",
      "pull_topic": "ams-topic-keycloak",
      "pull_sub": "ams-sub-keycloak",
      "token": "ams-token-keycloak",
      "pub_topic": "ams-publish-topic-keycloak",
      "poll_interval": 1
    },
    "auth_server": "https://example.com/auth",
    "realm": "example",
    "client_id": "client ID",
    "client_secret": "client secret"
  },
  "mitreid": {
    "ams": {
      "host": "example.host.com",
      "project": "ams-project-name-mitreid",
      "pull_topic": "ams-topic-mitreid",
      "pull_sub": "ams-sub-mitreid",
      "token": "ams-token-mitreid",
      "pub_topic": "ams-publish-topic-mitreid",
      "poll_interval": 1
    },
    "issuer": "https://example.com/oidc",
    "refresh_token": "refresh token",
    "client_id": "client ID",
    "client_secret": "client secret"
  },
  "ssp": {
    "ams": {
      "host": "example.host.com",
      "project": "ams-project-name-ssp",
      "pull_topic": "ams-topic-ssp",
      "pull_sub": "ams-sub-ssp",
      "token": "ams-token-ssp",
      "pub_topic": "ams-publish-topic-ssp",
      "poll_interval": 1,
      "deployer_name": "1"
    },
    "metadata_conf_file": "/path/to/ssp/metadata/file.php",
    "cron_secret": "SSP cron secret",
    "cron_url": "http://localhost/proxy/module.php/cron/cron.php",
    "cron_tag": "hourly",
    "request_timeout": 100
  },
  "log_conf": "conf/logger.conf"
}

As shown above there are three main groups, namely Keycloak, MITREid and SSP and each group can have its own AMS settings and service specific configuration values. The only global value is the log_conf path if you want to use the same logging configuration for both of the deployers. In case you need a different configuration for a deployer you can add log_conf in the scope of "MITREid" or "SSP".

ServiceRegistryAms

Use ServiceRegistryAms as a manager to pull and publish messages from AMS

from ServiceRegistryAms.PullPublish import PullPublish

with open('config.json') as json_data_file:
  config = json.load(json_data_file)
  ams = PullPublish(config)

  message = ams.pull(1)
  ams.publish(args)

Keycloak

Use Keycloak as an API manager to communicate with Keycloak

  • First obtain an access token and create the Keycloak API Client (find client_credentials_grant under Utils directory)
  access_token = client_credentials_grant(issuer_url, client_id, client_secret)
  keycloak_agent = KeycloakClientApi(issuer_url, access_token)
  • Use the following functions to create, delete and update a service on client_credentials_grant
  response = keycloak_agent.create_client(keycloak_msg)
  response = keycloak_agent.update_client(external_id, keycloak_msg)
  response = keycloak_agent.delete_client(external_id)

MITREid Connect

Use MITREid Connect as an API manager to communicate with MITREid

  • First obtain an access token and create the MITREid API Client (find refresh_token_grant under Utils directory)
  access_token = refresh_token_grant(issuer_url, refresh_token, client_id, client_secret)
  mitreid_agent = mitreidClientApi(issuer_url, access_token)
  • Use the following functions to create, delete and update a service on MITREid
  response = mitreid_agent.createClient(mitreid_msg)
  response = mitreid_agent.updateClientById(external_id, mitreid_msg)
  response = mitreid_agent.deleteClientById(external_id)

License

Apache

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

rciam_federation_registry_agent-4.0.1.tar.gz (23.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

rciam_federation_registry_agent-4.0.1-py2.py3-none-any.whl (28.3 kB view details)

Uploaded Python 2Python 3

File details

Details for the file rciam_federation_registry_agent-4.0.1.tar.gz.

File metadata

File hashes

Hashes for rciam_federation_registry_agent-4.0.1.tar.gz
Algorithm Hash digest
SHA256 654ecbf28eed3fa21d9d2f6b90b50d4d8b04917ffe363428758951786a410129
MD5 cd06aa0641187d90e71023e75524f3e9
BLAKE2b-256 4d80148cf60f5c50461c7e018ce979df2f0e236fdfe787e2b4d3fc23e6b68a6c

See more details on using hashes here.

File details

Details for the file rciam_federation_registry_agent-4.0.1-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for rciam_federation_registry_agent-4.0.1-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 c0efa9f841ff95c7fdf2f1e61487fb09d350a4a3782e02fcae2d5fcedeffc404
MD5 58cc5893ce138f08bfec812a30701c73
BLAKE2b-256 ce3a59f40ff87571894631a9c152d34526eb920a2845101ec3e6e7bb07b5a6fb

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page