Library for signing XML documents.
Validate XML, Parse XML, Build XML without C/C++ based libraries
A convertor between XML text and Javascript object / JSON text.
An evented streaming XML parser in JavaScript
XML utilities for the AWS SDK
Build XML from JSON without C/C++ based libraries
Utilities for determining if characters belong to character classes defined by the XML specs.
Validates XML name productions — Name, NCName, QName, NMToken, NMTokens — for XML 1.0 and 1.1
An evented streaming XML parser in JavaScript
Validates whether a string matches the production for an XML name or qualified name
Fast and simple xml generator. Supports attributes, CDATA, etc. Includes tests and examples.
Simple XML to JavaScript object converter.
Apple's property list parser/builder for Node.js and browsers
XML language support for the CodeMirror code editor
Xml digital signature and encryption library for Node.js
An XML builder for node.js
Convert XML to JSON - Fast & Simple
⚠️ This is an internal package; you don't need to install it in order to use the junit formatter in `@cucumber/cucumber` as it's built in there.
Converts a XML string into a human readable format (pretty print) while respecting the xml:space attribute
Parse a XML string into a proprietary syntax tree
lezer-based XML grammar
adds node crypto signing for browsers
XML Parser Implemented in JavaScript
An evented streaming XML parser in JavaScript
Adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, and the [XML Signature Syntax and Processing](http://www.w3.org/TR/xmldsig-core/) standard by wrapping around the [xmlsec](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`. Implementation is based off nokogiri-xmlsec by Colin MacKenzie IV with very heavy modifications.
This gem provides functionality to sign XML using a PKCS12 certificate, Nokogiri, and OpenSSL
Adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, and the [XML Signature Syntax and Processing](http://www.w3.org/TR/xmldsig-core/) standard by wrapping around the [xmlsec](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`. Implementation is based off nokogiri-xmlsec by Colin MacKenzie IV with very heavy modifications.
Adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, by wrapping around the [xmlsec](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`.
This is a fork of nokogiri-xmlsec. This fork uses mini_portile to improve code predictiveness and allow heroku deploys. This gem adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, by wrapping around the [xmlsec1](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`.
Adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, by wrapping around the [xmlsec](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`.
The saml2 library is yet another SAML library for Ruby, with an emphasis on _not_ re-implementing XML, especially XML Security, _not_ parsing via Regex or generating XML by string concatenation, _not_ serializing/re-parsing multiple times just to get it into the correct format to sign or validate.
Adds support to Ruby for encrypting, decrypting, signing and validating the signatures of XML documents, according to the [XML Encryption Syntax and Processing](http://www.w3.org/TR/xmlenc-core/) standard, by wrapping around the [xmlsec](http://www.aleksey.com/xmlsec) C library and adding relevant methods to `Nokogiri::XML::Document`.
Libsaml makes the creation of SAML 2.0 messages easy. The object structure is modeled after the SAML Core 2.0 specification from OASIS. Supported bindings are HTTP-Post, HTTP-Redirect, HTTP-Artifact and SOAP. Features include XML signing, XML verification and a pluggable backend for providers (FileStore backend included).
SAML 2.0 is an XML-based protocol that uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, that is, an identity provider, and a SAML consumer, that is, a service provider. SAML 2.0 enables web-based authentication and authorization scenarios including cross-domain single sign-on (SSO), which helps reduce the administrative overhead of distributing multiple authentication tokens to the user.
REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## 🎯 Main Features ### 📄 Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search) ### ✅ Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification ### 📋 Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### 📊 Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments) ### 📡 AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user ### 🏛️ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete ## 🔒 Authentication All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token? #### 🔑 Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended** for integration in your applications and CI/CD workflows. **Prerequisites:** Having set a password on your account **For users registered via email/password:** - You already have a password, use it directly **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "your_email@example.com", "password": "your_password" }' ``` **Optional `client_uid` parameter:** To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "your_email@example.com", "password": "your_password", "client_uid": "550e8400-e29b-41d4-a716-446655440000" }' ``` The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client **Response:** ```json { "access": "eyJ0eXAiOiJKV1QiLCJhbGc...", // Access token (validity: 30 min) "refresh": "eyJ0eXAiOiJKV1QiLCJhbGc..." // Refresh token (validity: 7 days) } ``` **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool #### 🖥️ Method 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable for quick tests or occasional use via the graphical interface. **How it works:** - Log in to the dashboard - Use the "Generate Test Token" or "Generate Production Token" buttons - Works for **all** users (OAuth and email/password), without requiring a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation ### 📚 Full Documentation For more information on authentication and API usage: https://factpulse.fr/documentation-api/
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.