Your OAuth 2.0 authorization server and OpenID provider start to run right after sign up.
Rocket Start
Your authorization server and OpenID provider start to run right after sign up.
For rocket start, you can use the default implementations of OAuth 2.0 and OpenID Connect endpoints provided by Authlete. At the same time, you can build your own for customization using Authlete Web APIs.
Cloud Style
Authlete has implemented functionalities of OAuth 2.0 and OpenID Connect as a BaaS.
The database is hosted on the cloud side, so you don't have to maintain it by yourself. Still, all the functionalities can be controlled via Web APIs, so you can incorporate them into any platforms you like.
Authorization Focus
Authorization and end-user authentication are carefully separated by the architecture.
This enables you to integrate Authlete with any end-user authentication mechanism. This means that you can add OAuth 2.0 and OpenID Connect functionalities into your existing web service seamlessly.
Multiple Servers
You can run multiple authorization servers with different configurations.
As your company grows, you may feel like adding new Web services, and meanwhile you will want to have the services share end-user accounts. Authlete architecture can support such a use case.
Web Consoles
Web consoles to manage servers and client applications are provided.
You can even let third-party developers use the developer console so that they can manage their client applications for your services if you implement a callback endpoint to authenticate developers.
Developer Friendly
Error responses from Authlete contain fine- grained error codes and detailed messages.
This helps developers of Web services and client applications locate their bugs quickly. For example, "[A011303] 'redirect_uri' parameter must be explicitly specified when 'scope' parameter contains 'openid'."
Service Owner Console
You can create and manage multiple authorization servers & OpenID providers by Service Owner Console.
Numerous parameters related to RFC 6749 (OAuth 2.0), OpenID Connect Core 1.0, OpenID Connect Discovery 1.0, and other specifications can be configured by Service Owner Console.
Developer Console
You have to provide third-party developers (and yourself) with a Web console for them to manage their client applications, but you are free from developing such a tool. Authlete offers Developer Console and you can let your third-party developers use it.
Numerous parameters related to RFC 6749 (OAuth 2.0), OpenID Connect Core 1.0, OpenID Connect Dynamic Client Registration 1.0, and other specifications can be configured by Developer Console.