Skip to main content

SAP Python Security Library

Project description

REUSE status

Description

This project is a python client library called sap-xssec for validation of OAuth access tokens issued by the XSUAA.

OAuth Authorization Code Flow

The typical web application use the OAuth authorization code flow for authentication, which is described as follows:

  1. A user accesses the web application using a browser.
  2. The web application (in typical SAP Cloud Platform applications, this is an application router) acts as OAuth client and redirects to the OAuth server for authorization.
  3. Upon authentication, the web application uses the code issued by the authorization server to request an access token.
  4. The web application uses the access token to request data from the OAuth resource server. The OAuth resource server validates the token using online or offline validation. For this validation libraries like sap-xssec are used.

alt text

Usage

For the usage of this library it is necessary to pass a JWT access token that should be validated to the library. The examples below rely on users and credentials that you should substitute with the ones in your context.

The typical use case for calling this API lies from within a container when an HTTP request is received and it must be checked if the requester is authorized to execute this method. In this case, the access token is contained in the authorization header (with keyword bearer). You can remove the prefix bearer and pass the remaining string (just as in the following example as access_token) to the API.

from sap import xssec
from cfenv import AppEnv

env = AppEnv()
uaa_service = env.get_service(name='<uaa_service_name>').credentials

security_context = xssec.create_security_context(access_token, uaa_service)

Note: That the example above uses module cfenv to retrieve the configuration of the uaa service instance. uaa_service is a dict that contains the necessary client information and looks like:

{
    'clientid' : 'example_clientid'               // the id of the client
    'clientsecret': 'example_clientsecret'        // the secret of the client
    'url': 'example_url'                          // the url of the uaa
    'uaadomain': 'example_uaadomain'              // the domain of the uaa
    'verificationkey': 'example_verification key' // (optional) the key used for the verfication of the token
}

If the uaadomain is set in the uaa_service and the jku and kid are set in the incomming token, the key is requested from the uaa. As a fallback, the verificationkey configured in uaa_service is used for offline validation. Requested keys are cached for 15 minutes to avoid extensive load on the uaa.

The creation function xssec.create_security_context is to be used for an end-user token (e.g. for grant_type password or grant_type authorization_code) where user information is expected to be available within the token and thus within the security context.

create_security_context also accepts a token of grant_type client_credentials. This leads to the creation of a limited SecurityContext where certain functions are not available. For more details please consult the API description in the wiki.

For example, the security_context object can then be used to check if a user has a required scope:

security_context.check_scope('uaa.user')

or to receive the client id of a user:

security_context.get_clientid()

More details on the API can be found in the wiki.

Offline Validation

sap-xssec offers offline validation of the access token, which requires no additional call to the UAA. The trust for this offline validation is created by binding the XS UAA service instance to your application. Inside the credentials section in the environment variable VCAP_SERVICES, the key for validation of tokens is included. By default, the offline validation check will only accept tokens intended for the same OAuth2 client in the same UAA identity zone. This makes sense and will cover the vast majority of use cases.

⚠️From version 2.1.0, the SAP_JWT_TRUST_ACL environment variable is no longer supported.

If you want to enable another (foreign) application to use some of your application's scopes, you can add a granted-apps marker to your scope in the xs-security.json file (as in the following example). The value of the marker is a list of applications that is allowed to request a token with the denoted scope.

{
  "xsappname"     : "sample-leave-request-app",
  "description"   : "This sample application demos leave requests",
  "scopes"        : [ { "name"                : "$XSAPPNAME.createLR",
                        "description"         : "create leave requests" },
                      { "name"                : "$XSAPPNAME.approveLR",
                        "description"         : "approve leave requests",
                        "granted-apps"        : ["MobileApprovals"] }
                    ],
  "attributes"    : [ { "name"                : "costcenter",
                        "description"         : "costcenter",
                        "valueType"           : "string"
                    } ],
  "role-templates": [ { "name"                : "employee",
                        "description"         : "Role for creating leave requests",
                        "scope-references"    : [ "$XSAPPNAME.createLR","JobScheduler.scheduleJobs" ],
                        "attribute-references": [ "costcenter"] },
                      { "name"                : "manager",
                        "description"         : "Role for creating and approving leave requests",
                        "scope-references"    : [ "$XSAPPNAME.createLR","$XSAPPNAME.approveLR","JobScheduler.scheduleJobs" ],
                        "attribute-references": [ "costcenter" ] }
                    ]
}

Configuration

To configure whether the sap-jwt or the py-jwt library should be used for validation of the jwt token, change the USE_SAP_PY_JWT environment variable to true.

⚠️From version 4.0.0, the USE_SAP_PY_JWT environment variable is no longer supported and therefore py-jwt is installed by default.

Requirements

sap-xssec requires python 3.8 or newer.

Download and Installation

As this package is deployed to PyPI, you can simply add sap-xssec as a dependency to your python project or install this package by running pip install sap-xssec.

Known Issues

How to obtain support

Open an issue in GitHub.

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

sap_xssec-4.4.0.tar.gz (33.4 kB view details)

Uploaded Source

Built Distribution

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

sap_xssec-4.4.0-py2.py3-none-any.whl (25.3 kB view details)

Uploaded Python 2Python 3

File details

Details for the file sap_xssec-4.4.0.tar.gz.

File metadata

  • Download URL: sap_xssec-4.4.0.tar.gz
  • Upload date:
  • Size: 33.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.9.25

File hashes

Hashes for sap_xssec-4.4.0.tar.gz
Algorithm Hash digest
SHA256 421d0f49f5fd08e499d1bbe2582225ed75678a3c485ece41841f495b5ea7a3bf
MD5 843de6129ec8fdb885cb4b65b028b7e5
BLAKE2b-256 fd5da987e51de4b3560f4064ef646ae5e7122e1f8026ad1b7eac7cd9cb796ec5

See more details on using hashes here.

File details

Details for the file sap_xssec-4.4.0-py2.py3-none-any.whl.

File metadata

  • Download URL: sap_xssec-4.4.0-py2.py3-none-any.whl
  • Upload date:
  • Size: 25.3 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.9.25

File hashes

Hashes for sap_xssec-4.4.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 66fe8c7500aa617fc7c72d86209789dad5e99d822c998823675b4f8aa08b7680
MD5 a9e271d3219b4bcee6acd46dbfce1870
BLAKE2b-256 c2dce42d5bf84f0c4dd3428ebeb9491bc54565cd0c705ca9ab43f2c1b79171ff

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