Libraries tagged by certify
jalle19/certificate-parser
166282 Downloads
A proper SSL/TLS certificate parser library for PHP
simplesamlphp/simplesamlphp-module-authx509
6638565 Downloads
A module that is able to authenticate users based on X509 client certificates
sevaske/php-zatca-xml
38345 Downloads
An unofficial PHP library for generating ZATCA Fatoora e-invoices. This library facilitates the creation of compliant e-invoices, QR Codes, and certificates, as well as the submission of e-invoices to ZATCA's servers. It provides developers with an easy-to-use, customizable, and robust toolkit to integrate and automate ZATCA e-invoicing processes in PHP applications.
setasign/cloud-kms-csr
41412 Downloads
Tools to create and update certificate signing requests (CSRs) and self-signed certificates with keys from cloud key management systems (AWS KMS and Google Cloud KMS)
stayallive/certificate-chain-resolver
6288 Downloads
Certificate chain resolver.
google/cloud-certificate-manager
283908 Downloads
Google Cloud Certificate Manager Client for PHP
certificationy/certificationy
31728 Downloads
A library to create certification system
centarro/certified-projects
44033 Downloads
Drupal Commerce related projects maintained by Centarro to the same standards as Commerce Core.
lyquidity/requester
99937 Downloads
Library to query HTTPS Certificates revocation status using the Online Certificate Status Protocol (OCSP) and to make a request to a Timestamp authority (TSA)
kelunik/acme-client
5027 Downloads
Let's Encrypt / ACME client written in PHP for the CLI.
certificationy/symfony-pack
29289 Downloads
A series of questions to prepare for the certification Symfony2
kdyby/curl-ca-bundle
245117 Downloads
This package provides root certificates for usage in api clients on systems that have missing or outdated certificates.
zerossl/cli-client
14232 Downloads
Create certificates and CSRs locally and easy in the CLI using newest PHP OpenSSL features and ZeroSSL for signing.
widop/google-analytics
635339 Downloads
Google certificate-based authentication in server-to-server interactions with google analytics
vitexsoftware/rbczpremiumapi
1812 Downloads
##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.