Search results

pki-symkey-10.0.7-1.fc19.x86_64

The Symmetric Key Java Native Interface (JNI) package supplies various native symmetric key operations to Java programs. This package is a part of the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains ALL top-level java-based Tomcat PKI components: * pki-symkey * pki-base * pki-tools * pki-selinux (f17 only) * pki-server * pki-ca * pki-kra (fedora only) * pki-ocsp (fedora only) * pki-tks (fedora only) * pki-javadoc which comprise the following corresponding PKI subsystems: * Certificate Authority (CA) * Data Recovery Manager (DRM) (fedora only) * Online Certificate Status Protocol (OCSP) Manager (fedora only) * Token Key Service (TKS) (fedora only) For deployment purposes, PKI Core contains fundamental packages required by BOTH native-based Apache AND java-based Tomcat Certificate System instances consisting of the following components: * pki-tools * pki-selinux (f17 only) Additionally, PKI Core contains the following fundamental packages required ONLY by ALL java-based Tomcat Certificate System instances: * pki-symkey * pki-base * pki-tools * pki-server PKI Core also includes the following components: * pki-javadoc Finally, if Certificate System is being deployed as an individual or set of standalone rather than embedded server(s)/service(s), it is strongly recommended (though not explicitly required) to include at least one PKI Theme package: * dogtag-pki-theme (Dogtag Certificate System deployments) * dogtag-pki-server-theme * redhat-pki-server-theme (Red Hat Certificate System deployments) * redhat-pki-server-theme * customized pki theme (Customized Certificate System deployments) * <customized>-pki-server-theme NOTE: As a convenience for standalone deployments, top-level meta packages may be provided which bind a particular theme to these certificate server packages.

pki-symkey-10.0.7-1.fc19.x86_64

The Symmetric Key Java Native Interface (JNI) package supplies various native symmetric key operations to Java programs. This package is a part of the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains ALL top-level java-based Tomcat PKI components: * pki-symkey * pki-base * pki-tools * pki-selinux (f17 only) * pki-server * pki-ca * pki-kra (fedora only) * pki-ocsp (fedora only) * pki-tks (fedora only) * pki-javadoc which comprise the following corresponding PKI subsystems: * Certificate Authority (CA) * Data Recovery Manager (DRM) (fedora only) * Online Certificate Status Protocol (OCSP) Manager (fedora only) * Token Key Service (TKS) (fedora only) For deployment purposes, PKI Core contains fundamental packages required by BOTH native-based Apache AND java-based Tomcat Certificate System instances consisting of the following components: * pki-tools * pki-selinux (f17 only) Additionally, PKI Core contains the following fundamental packages required ONLY by ALL java-based Tomcat Certificate System instances: * pki-symkey * pki-base * pki-tools * pki-server PKI Core also includes the following components: * pki-javadoc Finally, if Certificate System is being deployed as an individual or set of standalone rather than embedded server(s)/service(s), it is strongly recommended (though not explicitly required) to include at least one PKI Theme package: * dogtag-pki-theme (Dogtag Certificate System deployments) * dogtag-pki-server-theme * redhat-pki-server-theme (Red Hat Certificate System deployments) * redhat-pki-server-theme * customized pki theme (Customized Certificate System deployments) * <customized>-pki-server-theme NOTE: As a convenience for standalone deployments, top-level meta packages may be provided which bind a particular theme to these certificate server packages.

pyDes-2.0.1-1.lbn19.noarch

This algorithm is a pure python implementation of the DES and Triple DES algorithms. Triple DES is either DES-EDE3 with a 24 byte key, or DES-EDE2 with a 16 byte key.

pyldb-1.1.16-1.fc19.armv6hl

Python bindings for the LDB library

pyldb-1.1.26-1.lbn19.x86_64

Python bindings for the LDB library

pyldb-1.1.26-1.lbn19.x86_64

Python bindings for the LDB library

python-authentic2-2.1.20-1.lbn19.noarch

Authentic 2 is a versatile identity provider aiming to address a broad range of needs, from simple to complex setups; it has support for many protocols and can bridge between them. Authentic 2 is under the GNU AGPL version 3 licence. It has support for SAMLv2 thanks to Lasso, a free (GNU GPL) implementation of the Liberty Alliance specifications. Full documentation available on http://packages.python.org/authentic2. Features -------- Authentic can authenticate users against: - an LDAP directory, - a SAML 2.0 identity provider, - an OpenID identity provider, - with an X509 certificate. Authentic can provide authentication to web applications using the following protocols: - OpenID, - SAML 2.0, - CAS 1.0 & CAS 2.0. Authentic can proxy authentication between any two different protocols it support.

python-authentic2-auth-saml2-1.0.4-1.g01a1c2d.lbn19.noarch

Authentic2 SAML2 authentication plugin

python-authentic2-idp-oauth2-1.0.14-2.lbn19.noarch

Settings AUTOMATIC_GRANT: A list of URL prefix which are automatically granted scopes without asking the user. Example: A2_OAUTH2_AUTOMATIC_GRANT = ( ('http://localhost:8000/', ('read',)), ) Web Service proxy You can configure simple REST web-service in /admin/authentic2_idp_oauth2/webservice/. URL field can contain template variable like that: http://example.com/info/?user={{ user.username|urlencode }} or like: http://example.com/categories/?format=json&NameID={{ federations.service_1.links.0|urlencode }} Supported authentication mechanisms on the target web-service are HMAC-SHA-256 and HMAC-SHA-1 as specified on http://doc.entrouvert.org/portail-citoyen/dev/. You can access your newly proxy web-service through those URLs: http://your-idp.com/idp/oauth2/ws-proxy/<web-service.id>/ or: http://your-idp.com/idp/oauth2/ws-proxy/<web-service.slug>/

python-django-allauth-0.18.0-1.lbn19.noarch

Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication. Home page http://www.intenct.nl/projects/django-allauth/ Source code http://github.com/pennersr/django-allauth Mailinglist http://groups.google.com/group/django-allauth Documentation http://django-allauth.readthedocs.org/en/latest/ Stack Overflow http://stackoverflow.com/questions/tagged/django-allauth Rationale Most existing Django apps that address the problem of social authentication focus on just that. You typically need to integrate another app in order to support authentication via a local account. This approach separates the worlds of local and social authentication. However, there are common scenarios to be dealt with in both worlds. For example, an e-mail address passed along by an OpenID provider is not guaranteed to be verified. So, before hooking an OpenID account up to a local account the e-mail address must be verified. So, e-mail verification needs to be present in both worlds. Integrating both worlds is quite a tedious process. It is definitely not a matter of simply adding one social authentication app, and one local account registration app to your INSTALLED_APPS list. This is the reason this project got started -- to offer a fully integrated authentication app that allows for both local and social authentication, with flows that just work. Commercial Support This project is sponsored by IntenCT. If you require assistance on your project(s), please contact us: info@intenct.nl.