Need help with authing?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

289 Stars 24 Forks 59 Commits 0 Opened issues


🔥Authing - IDaaS/IAM solution that can Auth to web and mobile applications.

Services available


Need anything else?

Contributors list


Authing —— IDaaS Provider that can Auth to Everything

Authing can help you rapidly integrate authentication and authorization for web, mobile, and legacy applications so you can focus on your core business.

We have deployed a cloud version, welcome to visit to try it out.

What is Authing

Authing provides authentication and authorization as a service.

We are here to give developers and companies the building blocks they need to secure their applications without having to become security experts.

You can connect any application (written in any language or on any stack) to Authing and define the identity providers you want to use (how you want your users to log in).

Based on your app's technology, choose one of our SDKs (or call our API), and hook it up to your app. Now each time a user tries to authenticate, Authing will verify their identity and send the required information back to your app.

Develop Roadmap: Authing Roadmap.

What is IDaaS ?

Identity as a Service (IDaaS) is a new generation of cloud computing application, which is also called Authentication as a service (AaaS) in some occasions. IDaaS is a cloud infrastructure provided by a third party to solve the problems of identity authentication and user management.

IDaaS provides secure access and data storage. When a user or an app attempts to access a protected resource, he must provide authentication information. For example, if you want to use Facebook, you must provide the account password. For example, when you vote on some wechat pages, the system will obtain your wechat personal information. In this scenario, authentication service, as a middleware, ensures that compliant users refuse illegal requests. When the authentication process is over, users can normally access the resources or application dashboard they want to access.

IDaaS generally need to support multiple languages:

  1. Java/Kotlin - used to develop Andorid or Web applications.
  2. Node/Python/PHP/Go/Dart/Rust... - used to develop Back-end applications.
  3. JavaScript - used to develop Web or Desktop applications.
  4. Swift/Flutter/OC - used to develop iOS applications.

There's a huge amount of work to support all these languages, and IDaaS makes it easy because it has integrated all the technology stacks since it was born.

Why Authing

  • You built an awesome app and you want to add user authentication and authorization. Your users should be able to log in either with username/password or with their social accounts (Facebook, Twitter, and so on). You want to retrieve the user's profile after the login so you can customize the UI and apply your authorization policies.
  • You built an API and you want to secure it with OAuth 2.0.
  • You have more than one app, and you want to implement Single Sing On.
  • You built a JavaScript front-end app and a mobile app, and you want them both to securely access your API.
  • You have a web app which needs to authenticate users using SAML.
  • You believe passwords are broken and you want your users to log in with one-time codes delivered by email or SMS.
    Click here to see more reasons
  • If one of your user's email addresses is compromised in some site's public data breach, you want to be notified, and you want to notify the users and/or block them from logging in to your app until they reset their password.
  • You want to act proactively to block suspicious IP addresses if they make consecutive failed login attempts, in order to avoid DDoS attacks.
  • You are part of a large organization who wants to federate their existing enterprise directory service to allow employees to log in to the various internal and third-party applications using their existing enterprise credentials.
  • You don't want (or you don't know how) to implement your own user management solution. Password resets, creating, provisioning, blocking, and deleting users, and the UI to manage all these. You just want to focus on your app.
  • You want to enforce multi-factor authentication when your users want to access sensitive data.
  • You are looking for an identity solution that will help you stay on top of the constantly growing compliance requirements of SOC2, GDPR, OpenID Connect, and others.
  • You want to use analytics to track users on your site or application. You plan on using this data to create funnels, measure user retention, and improve your sign up flow.


  1. Mainstream third-party social login integrations(Wechat, QQ, Github, Weibo, DingTalk, Alipay).
  2. SSO based on OAuth2.0, OpenID Connect, SAML, LDAP and CAS.
  3. User management system based on Web (authorization management, identity management, basic data crud).
  4. Role Based Access Control to authorizate users.
  5. User's geographical location record, login and registration history, easy to audit.
  6. Multifactor Authentication System.
  7. Cross platform integration capability (Android, iOS, Web).
  8. Multi language SDK (JavaScript, Node, Java, Python, OC, PHP, 小程序, ReactNative).
  9. Secure identity authentication based on HTTPS, JWT, MD5, RSA, sha256, salt.
  10. Mail service based on message queue, mail template configuration service based on Web and the ability to customize the third-party mail provider.
  11. Easy to integrate and expand plug-in system and access to programmable rules.
  12. User login location and IP monitoring.
  13. Use the Wechat Miniprogram to scan the QRCode to log in.
  14. Easy implementation of web page QRCode scanning login in app.
  15. Log in with mobile phone verification code.
  16. Six lines of code generates a cross-platform login form.
Which industry standards does Authing use? Once upon a time, when computers were standalone systems, all the authentication and user data lived in a single machine. Times have changed, and now you can use the same login information across multiple apps and sites. This has been achieved through widespread adoption of identity industry standards across the web.

These are a set of open specifications and protocols that specify how to design an authentication and authorization system. They specify how you should manage identity, move personal data securely, and decide who can access applications and data.

The identity industry standards that we use here in Authing are:

  • OAuth 2: an authorization standard that allows a user to grant limited access to their resources on one site, to another site, without having to expose their credentials. You use this standard every time you log in to a site using your Google account and you are asked if you agree with sharing your email address and your contacts list with that site.
  • Open ID Connect: an identity layer that sits on top of OAuth 2 and allows for easy verification of the user's identity, as well the ability to get basic profile information from the identity provider.
  • JSON Web Tokens: an open standard that defines a compact and self-contained way for securely transmitting information between parties as a JSON object.
  • Security Assertion Markup Language (SAML): an open-standard, XML-based data format that allows businesses to communicate user authentication and authorization information to partner companies and enterprise applications their employees may use.
Click here to see part of screenshots of Authing

Built With

  1. TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
  2. Nest.js - A progressive Node.js framework.
  3. Vue.js - A JavaScript framework for building UI on the web.
  4. MongoDB - A NoSQL Database.
  5. GraphQL - A query language and execution engine tied to any backend service.
  6. Docker - Containers.
  7. RabbitMQ - Open source multi-protocol messaging broker.


Under Construction.


Under Construction.


Document of authing is Deployed on Gitbook:

  1. Mainland China users please visit:
  2. Non mainland China users please visit:

Videos And Articles

  1. Authing 是什么以及为什么需要 Authing
  2. 为什么身份认证值得上云
  3. 一键认证让移动应用都不需要发短信了,Web 怎么办?
  4. 函数计算在身份认证云中的应用场景
  5. 用 Authing 10 分钟实现单点登录
  6. Serverless 最佳实践:在云上认证身份授权资源
  7. 为什么所有软件都应该使用单点登录来管理用户?
  8. 身份上云 or 自建?这里有 20 个问题值得你思考
  9. Auth0 和 Authing,谁是身份云的高脚杯
  10. 五分钟接入微信网页授权登录
  11. 六个步骤实施零信任网络
  12. 五分钟实现小程序登录
  13. Authing 开发资源最全合集
  14. 五分钟在移动端实现完整用户认证
  15. 使用 Authing 快速集成 AWS 服务
  16. 从几个细节看身份认证这件事不简单
  17. GraphQL 在身份认证场景中的深度使用实践(一)

Who Uses Authing?

Users are encouraged to add themselves to the Powered By page.


Under Construction.


  1. Join us on Gitter: #authing-chat
  2. QQ group: 543317789





We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.