Skip to main content

SATOSA Frontend based on idetity python oidcop

Project description

SATOSA oidcop frontend

CI build Python version Downloads Downloads per week License

SATOSA Frontend based on identity python oidcop.

Features

Endpoints:

  • provider discovery
  • jwks uri
  • authorization
  • token
  • userinfo
  • registration
  • registration_read endpoint
  • introspection endpoint
  • token exchange

Requirements

Setup

pip install satosa_oidcop

Configuration

Anyone can migrate its oidcop configuration, from flask_op or django-oidc-op or whatever, in SATOSA and without any particular efforts. Looking at the example configuration we see that config.op.server_info have a standard SATOSA configuration with the only addition of the following customizations, needed in SATOSA for interoperational needs. These are:

  • autentication
        authentication:
          user:
            acr: urn:oasis:names:tc:SAML:2.0:ac:classes:InternetProtocolPassword
            class: satosa.frontends.oidcop.user_authn.SatosaAuthnMethod
  • userinfo
       userinfo:
         class: satosa.frontends.oidcop.user_info.SatosaOidcUserInfo

authentication inherits oidcop.user_authn.user.UserAuthnMethod and overloads two methods involved in user authentication and verification. These tasks are handled by SATOSA in its authentication backends.

userinfo inherits oidcop.user_info.UserInfo and proposes a way to store the claims of the users when they comes from the backend. The claims are stored in the session database (actually mongodb) and then they will be fetched during userinfo endpoint (and also token endpoint, for having them optionally in id_token claims).

SSO and cookies

oidcop SSO and cookies were not have been implemented because SATOSA doesn't support logout, because of this they are quite useless at this moment.

Client and Session Storage

MongoDB is the storage, here some brief descriptions for a demo setup. The interface to SATOSA oidcop storage is satosa.frontends.oidcop.storage.base.SatosaOidcStorage and it has three methods:

  • get_client_by_id(self, client_id:str, expired:bool = True)
  • store_session_to_db(self, session_manager, **kwargs)
  • load_session_from_db(self, req_args, http_headers, session_manager, **kwargs)

satosa.frontends.oidcop.storage.mongo.Mongodb overloads them to have I/O operations on mongodb.

Subject type

The client configuration can also include the subject_type key, with permitted values being public and pairwise. If absent, the default is to choose public. This has been driven by backwards compatibility with existing behaviour: oidcop (session_manager.create_session) defaults to public.

For user privacy, we strongly recommend selecting pairwise for new deployments, unless public is absolutely needed (for linking users across related but distinct services).

Demo

Satosa-Saml2Spid is a custom Satosa configuration to deal with many SAML2 and OIDC Relying parties and many eduGain and SPID Identity Provider.

satosa_oidcop

Contributions

Feel free to open issues and pull requests, we build communities!

Developer notes

Storage design

At this time the storage logic is based on oidcop session_manager load/dump/flush methods. Each time a request is handled by an endpoint the oidcop session manager loads the definition from the storage, only which one are strictly related to the request will be loaded in the in memory storage of oidcop.

Roadmap

Tests

Before you run the tests mind that you've to start a local mongod instance, e.g. with:

docker run --rm -e ALLOW_EMPTY_PASSWORD=yes -e MONGODB_ENABLE_JOURNAL=false -p 27017:27017 --name mongodb bitnami/mongodb:latest

Then run the tests:

pip install pytest pytest-cov
pytest --cov=satosa_oidcop -v --cov-report term --cov-fail-under=95 tests/

Authors

  • Giuseppe De Marco Università della Calabria

Credits

  • Roland Hedberg
  • Andrea Ranaldi ISPRA Ambiente
  • Identity Python Community

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

satosa_oidcop-1.1.1.tar.gz (27.6 kB view details)

Uploaded Source

Built Distribution

satosa_oidcop-1.1.1-py3-none-any.whl (27.8 kB view details)

Uploaded Python 3

File details

Details for the file satosa_oidcop-1.1.1.tar.gz.

File metadata

  • Download URL: satosa_oidcop-1.1.1.tar.gz
  • Upload date:
  • Size: 27.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.10.9

File hashes

Hashes for satosa_oidcop-1.1.1.tar.gz
Algorithm Hash digest
SHA256 aacd2f940b0cde273e8059948c975b8c5572971c5829d174be1755821ef4bdda
MD5 b26c2be12852eef95a2ae4fe4a12e19a
BLAKE2b-256 8d8fcd805dad54051dc69cb9c1afd931cd1323a594e9b97b94e5038dfdafb2bb

See more details on using hashes here.

File details

Details for the file satosa_oidcop-1.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for satosa_oidcop-1.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 7d709d9b9c8fbf028232d3d037770019173bb0a214dee6addfb75c2bea72f54f
MD5 304eb1e035cb1081395b70a7c07a1a52
BLAKE2b-256 93f51886a266841dc7128f174cf2042dbb489ab0f6bc5b0ea90ee5aa23b31a15

See more details on using hashes here.

Supported by

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