Search Results :
×Our trusted Customers
Users can authenticate themselves using their username and password using basic authentication.
When users authenticate using an API, a unique token is generated to verify the user’s identity during the first login attempt.
Users can use the OAuth 2.0 authentication protocol to authorise one application to interact with another on their behalf without having to provide their password.
To allow users to authenticate the web application should send a Json Web Token (JWT) in the authorization header of an HTTP request to your Server-side.
Users will be able to authenticate their existing identities from third-party identity providers such as Google, Facebook, and LinkedIn without entering their password.
Support for integrating SSO for a decoupled Drupal site i.e. allowing your users to login to the Drupal backend as well as the front-end application
Based on user's Drupal roles/capabilities users can get access to his Drupal Dashboard and REST APIs for that site.
Default token expiry time provided is 1 hour. Using this feature admin can change the token expiry date as per his requirement.
Provide the Signature Verification and Validation along with JWT Token Validation. Also, an option to select the Signing Algorithm to validate the JWT token.
Default all the Drupal REST APIs will be protected. Using this feature admin can make some APIs to publicly accessible without authentication.
Default Authorization Header will be used to authenticate the requests. Using this feature admin can change Authorization header to any other header accordingly.
Supports JSON API module
Supports default REST APIs
API Key Authentication
Basic Authentication
Supports JSON API module
Supports default REST APIs
API Key Authentication
Basic Authentication
Access Token-Based Authentication
JWT Based Authentication
3rd Party/External IDP Token-Based Authentication
Generate separate API Keys for every user
Supports restriction of custom APIs
Custom Authentication Header
Configurable Token Expiry Time
Whitelist or Blacklist APIs
IP Address-Based Restriction
Role Based Restriction
Premium GoTo Meeting Support
A Drupal instance refers to a single installation of a Drupal site. It refers to each individual website where the module is active. In the case of multisite/subsite Drupal setup, each site with a separate database will be counted as a single instance. For eg. If you have the dev-staging-prod type of environment then you will require 3 licenses of the module (with additional discounts applicable on pre-production environments). Contact us at drupalsupport@xecurify.com for bulk discounts.
Credit cards (American Express, Discover, MasterCard, and Visa) - If the payment is made through Credit Card/International Debit Card, the license will be created automatically once the payment is completed.
Our primary focus is on providing secure Identity and Access Management solutions around a variety of popular use-cases such as Single Sign On, Two-factor Authentication (TFA/MFA), User Provisioning, LDAP, REST API Authentication, and much more. You can read other case studies that showcase our solutions.
We had to implement single sign-on functioning to the site while also performing syncing operations from their Identity provider to the Drupal site through System for Cross-Domain Identity Management(SCIM)
Read moreOne Headless Drupal website acting as a Service Provider and another Headless Drupal website acting as the Identity Provider.
Read moreConfiguring SSO using the OAuth PKCE Protocol on a complex Decoupled Drupal Website using a custom, widely popular Identity Provider (IdP)
Read moreWhat are the Benefits of our Drupal module?
Thank you for your response. We will get back to you soon.
Something went wrong. Please submit your query again
I am raw html block.
Click edit button to change this html