Authentiq Connect is an easy-to-use Identity Provider built on top of OpenID Connect that makes it easy for websites and apps to move beyond usernames and passwords while safeguarding the end-user’s privacy.
Continue reading on to explore features, use cases and frequently asked questsion.
Authentiq Connect supports a growing number of web standards to integrate applications with the best possible user experience.
|OAuth 2.0||code, token|
|OIDC Core||code, id_token, hybrid|
|OIDC Dynamic Client Registration||Supported|
|OIDC Session Management||Supported|
|OIDC Back-Channel Logout||Supported|
|OAuth 2.0 Multiple Response Types||Supported|
|OAuth 2.0 Form Post Response Mode||Supported|
|Security Event Tokens||Coming soon|
By enabling Authentiq you make the following authentication methods available to your site’s users.
|Passwordless||Authentiq ID||QR code, PN, Handle||Supported|
|Virtual 2FA||Authentiq ID, Google Authenticator||TOTP||Supported|
|Physical 2FA||YubiKey||USB Token||Coming soon|
|One-time authentication||Magic link||Coming soon|
These methods can work in addition to or conjunction with your existing login system.
We often see sites that already integrate with social login providers adding passwordless authentication via Authentiq ID, this way providing their users with a privacy-aware alternative to signing in with Google or Facebook.
Another common pattern is to use Authentiq Connect to effortlessly add two-step verification on top of usernames and passwords that are kept in-house.
The Authentiq ID mobile app (available on Android and iOS) are the key to your end-user’s privacy. It acts as a mobile identity wallet that can be used to identify to websites. A user’s Authentiq ID can be seen as their personal cryptographic passport that holds profile information.
When signing in, the user decides what information will be shared. Phone number and email address will already have been verified by Authentiq so that the website doesn’t have to.
When a user signs in with Authentiq ID, the website session is also visible in the mobile app. Walking away from a computer
Create rich integrations by listening to Authentiq’s Security Event Token webhooks. Use a webhook, for instance, to add new users to your newsletter easily. Coming soon.
On intranets authentication is often synchronized between applications. You can configure Authentiq Connect for Single Sign-on to support this. Coming soon.
The ability to get a different user ID for every site you log in to, protecting your privacy better in case a site is breached. Coming soon.
Authentiq Connect leverages OIDC’s scopes to specify what profile information to request from a user.
scopes from OIDC where possible.
||A user’s typical profile, including name||No|
|A user’s (verified) email address||Yes|
||A user’s (verified) phone number||Yes|
||A user’s home address||No|
||A user’s full name||No|
||A user’s current location||No|
||A user’s preferred username||No|
Requested scopes are optional by default, leaving the choice of providing any of the details to the end-user, who will be able to opt out of the requested scopes on the Authentiq ID consent screen.
As a website it is possible to mark essential scopes as required too, by appending
Get in touch with us on firstname.lastname@example.org.
Please report security issues to email@example.com.