dev-docs.qlikauth.com Open in urlscan Pro
18.172.153.98  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Skip to main content

QlikAuthDocsAPIChangelogs
3.9.12
 * Next
 * 3.9.12
 * 3.9.10
 * 3.9.9
 * 3.9.8
 * 3.9.7
 * 3.9.5
 * 3.9.4
 * 3.9.3
 * 3.9.2
 * 3.9.1
 * 3.9.0
 * 3.8.2
 * 3.8.1
 * 3.8.0
 * 3.6.0
 * 3.5.1
 * 3.5.0
 * 3.4.1
 * 3.4.0
 * 3.3.1
 * 3.3.0
 * 3.2.6
 * 3.2.5
 * 3.2.4
 * 3.2.3
 * 3.0.0
 * 2.6.0
 * 2.2.0-beta


ctrlK

 * QlikAuth
 * Application
 * Audit
 * Authentication
 * Branding
 * DNS
 * Email
 * Groups
 * Marketplace
 * Policies
 * Roles
 * SMS
 * Scopes
 * Security
 * Settings
 * Setup Guide
 * User Sync
 * Users
 * Workspace

 * 
 * QlikAuth

On this page


QLIKAUTH


QUICK START

 * QlikAuth collective platform has developed access management, identity
   management, user-managed access, directory services, and an identity gateway.
   Organizations can modify their components in QlikAuth to meet an endless
   number of identity use cases.

 * QlikAuth delivers configurable building pieces that will enable dynamic user
   journeys instead of depending on pre-defined behavior for authentication,
   permission, and enrollment.


WHAT IS IAM?

Identity and Access Management(IAM) is a set of corporate procedures, rules, and
technology that make managing electronic or digital identities easier. Admins
will regulate user access to vital data within their businesses by using an IAM
architecture. IAM systems include Single Sign-On(SS0), Two-Factor
Authentication(2FA), MultiFactor Authentication(MFA), and privileged access
management. These technologies also allow for the safe storage of identification
and profile data, as well as data governance mechanisms that guarantee that only
essential and relevant information is exchanged.

AUTHENTICATION VS AUTHORIZATION

Comparative ParametersAuthenticationAuthorizationDescriptionAuthentication is
the process of verifying a user's identity.The process of setting privileges for
a specific system is known as authorization.ProcedureIt checks to see if the
user is who he or she claims to be.It decides whether or not the user has access
to the resource.PreferenceAfter a successful authorization, authentication is
always performed.Authorization is always first and foremost.ActionAuthentication
is the process of confirming a user's claims.The user's eligibility to use the
system is checked during the authorization procedure.ExampleJohn was turned down
because he was unable to pass the authentication process.Our information might
be used for security purposes by the company's owner.


WHAT WE DO?

IDENTITY AND ACCESS MANAGEMENT

Manage identity connections across all channels, including on-premises, in the
cloud with ease. Enterprise - ready access management system with adaptive
smartness to secure against risk-based vulnerabilities and promote customization
across people, services,

SECURITY

Narrow the Internet - of - things(IoT) security gap and establish trusted
identity connections with a safe solution that combines contextual security,
open standards, and the ability to scale to handle IoT-level demands.

DIRECTORY SERVICES

Customer and user identification data can be shared in real time across
business, cloud, and social settings with this embeddable directory.


FEATURES

The following are some of the features that QlikAuth offers:

 * For browser apps, single-sign on and single-sign out are available.

 * Support for OpenID Connect.

 * Support for SAML.

 * Authenticate with external OpenID Connect or SAML Identity Providers using
   Identity Brokering.

 * Allow users to log in using Google, GitHub, Facebook, Twitter, and other
   social media platforms.

 * Sync users from LDAP and Active Directory servers using User Federation.

 * Session management - Administrators and users can both observe and manage
   user sessions.

 * Token mappers allow you to map user attributes, responsibilities, and other
   information into tokens and statements in whatever way you wish.

 * Policies for not-before revocation per realm, application, and user.


PROTOCOLS SUPPORTING

OPENID CONNECT

 * OpenID Connect (OIDC) is an OAuth 2.0-based authentication mechanism. OIDC is
   a full-fledged authentication and authorization protocol, whereas OAuth 2.0
   is merely a framework for constructing authorization protocols and is mostly
   underdeveloped. The Json Web Token (JWT) family of specifications is also
   widely used by OIDC. These standards describe a JSON format for
   identification tokens as well as methods for digitally signing and encrypting
   that data in a compact and web-friendly manner.

 * When it comes to OIDC, there are two sorts of use cases. The first is a
   programme that requests the server to authenticate a user on their behalf.
   The application will be given an identity token and an access token after a
   successful login. The identification token holds information about the user,
   including their username, email address, and other personal details.

 * A client who wishes to use distant services is the second sort of use case.
   In this example, the client requests from QlikAuth an access token that it
   will use to access other distant services on the user's behalf. QlikAuth
   verifies the user's identity before seeking permission to allow access to the
   client who has requested it. After that, the access token is delivered to the
   client. The realm has signed this access token digitally.

SAML

 * SAML 2.0 is a specification that is comparable to OIDC, however it is more
   older and more established. Because it is derived from SOAP and the abundance
   of WS-* specifications, it is a little more verbose than OIDC. SAML 2.0 is
   basically an authentication protocol that involves the authentication server
   and the application exchanging XML documents. Requests and answers are
   verified using XML signatures and encryption.

 * SAML is used in two ways in QlikAuth: browser apps and REST invocations.

 * When it comes to SAML, there are two sorts of use cases. The first is a
   programme that requests the QlikAuth server to authenticate a user on their
   behalf. Following a successful login, the application will get an XML
   document containing a SAML assertion, which describes several user
   properties. This XML document is tokenized by the realm and contains the
   necessary data (role mappings) that the application could use to identify
   what resources the user is permitted to access. The customer who wishes to
   access distant services is the second sort of use case. In this scenario, the
   client requests a SAML assertion from QlikAuth, which it may use to access
   additional remote services on the user's behalf.


SIMPLY NEED TO COMPLETE FEW STEPS TO BEGIN UTILIZING OUR PRODUCT

 * We create a new Workspace for you on signing up. A Workspace is a logically
   separated set of users who have similar access requirements but have
   different rights.

 * Integrate any application with your Workspace, as well as the identity
   providers that you want to utilize.

 * QlikAuth will now verify a user's identity and provide the necessary
   information back to your app every time they attempt to authenticate. You can
   also define tokens, Role-Based Access Control (RBAC), and other access
   settings and permissions by registering a custom API.

 * To ensure a consistent experience, integrate a flow to your application and
   configure your own SMS and Email provider details.

 * Configure how your Workspace and apps interact with one another to improve
   how you authenticate and authorize users.


Next
Access Token Lifespan
 * Quick Start
 * What is IAM?
 * What we do?
 * Features
 * Protocols Supporting
 * Simply need to complete few steps to begin utilizing our product

Copyright © 2023 QlikAuth.