> ## Documentation Index > Fetch the complete documentation index at: https://developers.authlete.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting up Authlete > A quick guide to try an OAuth 2.0 authorization flow using Authlete 2.x. This page is for **Authlete 2.x**. For current (3.0) documentation, see [Getting Started](/get-started/quickstarts/getting-started).
Try “OAuth 2.0 Authorization Flow” Using Authlete.

1. Create Your Account.

Fill in [the registration page](https://so.authlete.com/accounts/signup) and click Sign Up.

2. Check Your Inbox.

You will get an email from Authlete, describing instructions on how to try the OAuth 2.0 flow.
💡 You can try OAuth 2.0 flow right after the signup. The following settings have been configured:
  • An Authlete service instance
  • A default OAuth 2.0 authorization endpoint
  • Sample client application settings
{/* **Technical Note** You can find the API key of your first service and the client ID of your first client application in the email. Also, you can see them in Service Owner Console and Developer Console, respectively. The URLs of the consoles are as follows. Service Owner Console: `https://so.authlete.com/` Developer Console: `https://cd.authlete.com//` You can log in to Developer Console using the API key and secret of the service. Also, you can let other (third-party) developers use Developer Console of your service by implementing a developer authentication callback endpoint to authenticate the developers. Read "Developer Authentication Callback" for details. */}

3. Click "Authorization Endpoint" Button.

You will be navigated to a login page for authentication and authorization.
💡 The "Authorization Endpoint" button in the email will invoke an authorization request (implicit grant flow) from your Web browser to Authlete's default authorization endpoint. The actual URL of the request is: `https://api.authlete.com/api/auth/authorization/direct/?response_type=token&client_id=`

4. Enter Login Information.

Use the API key and secret of your Authlete service instance.
💡 For testing purposes, the default authorization endpoint authenticates a user with the API key and secret.

5. Click “Authorize” Button.

Your browser will be redirected to the client's redirection endpoint that shows an issued access token. You can find the same access token in the fragment part of the destination URL. `https://api.authlete.com/api/mock/redirection/#access_token=SNqzo...&token_type=Bearer&expires_in=86400&scope=`
Congratulations! You successfully issued your first access token using Authlete!

Try “Authorization Code Grant Flow”

Try “Authorization Code Grant Flow” in addition to Implicit Grant Flow in the previous section.
1. Enter the following URL (authorization request) to your Web browser and submit it. `https://api.authlete.com/api/auth/authorization/direct/?response_type=code&client_id=` This request is the same as the previous one except `response_type=code`. Replace `` / `` to the appropriate values in your environment.
2. You will be navigated to the login page. Enter the API key and the secret.
3. Your browser will be redirected to the client's redirection endpoint. Enter the value of `SAMPLE_APP_CLIENT_ID` to `client_id` field and click “Submit” button to make a token request.
4. Token response (JSON formatted) will be displayed. There should be values for `"access_token"` and `"refresh_token"`.

Authorization Server Implementations

In the previous section, you tried the flow using the default implementation of authorization endpoint. For real deployments, you have freedom of choice to implement your own authorization server using [Authlete Web APIs][api].
java-oauth-server is an open-source authorization server written using Authlete Web APIs. It is the reference implementation in Java and a good starting point for your own authorization server implementation.
This reference implementation uses Authlete as its backend so that it can eliminate efforts to set up a database server as storage of authorization data (e.g. access tokens), configuration data of the authorization server itself as well as client application settings communicating with the server. So you can download and start the authorization server only with a few commands as shown below: * [>Java (JAX-RS)](#oauth-server-jaxrs) * [Java (Spring)](#oauth-server-spring) * [C#](#oauth-server-csharp) * [PHP (Laravel)](#oauth-server-laravel)
Please check the [documents](https://github.com/authlete/java-oauth-server) at java-oauth-server for details.
```text theme={null} $ git clone https://github.com/authlete/java-oauth-server.git $ cd java-oauth-server $ vi authlete.properties $ mvn jetty:run ```
Please check the [documents](https://github.com/authlete/spring-oauth-server) at spring-oauth-server for details.
```text theme={null} $ git clone https://github.com/authlete/spring-oauth-server $ cd spring-oauth-server $ vi authlete.properties $ mvn spring-boot:run ```
Please check the [documents](https://github.com/authlete/csharp-oauth-server) at csharp-oauth-server for details.
```text theme={null} $ git clone https://github.com/authlete/csharp-oauth-server $ cd csharp-oauth-server/AuthorizationServer $ vi authlete.properties $ dotnet run ```
Please check the [documents](https://github.com/authlete/authlete-php-laravel) at authlete-php-laravel for details.
```text theme={null} $ laravel new authorization-server $ cd authorization-server $ composer require authlete/authlete-laravel $ php artisan authlete:authorization-server $ vi config/authlete.php ```
If you implement your own authorization server using Authlete Web APIs, you don't have to implement an [authentication callback endpoint][auth_cb], but instead you are required to customize some source files related to end-user authentication. ## Useful Links * [Authlete API Tutorials][tutorial] * Authlete API Tutorials explain how Authlete APIs work. * [Service Owner Console][so] * Service Owner Console is a Web console for you to manage services. * [Developer Console][cd] * Developer Console is a Web console for developer to manage client applications. * [Protected Resource][resource] * The main purpose to implement OAuth 2.0 is to protect Web APIs by access tokens.
[api]: https://docs.authlete.com/ [signup]: https://so.authlete.com/accounts/signup [java_oauth]: https://github.com/authlete/java-oauth-server [6749]: https://tools.ietf.org/html/rfc6749 [tutorial]: /developers/tutorial [so]: /developers/so_console [cd]: /developers/cd_console [resource]: /developers/definitive_guide/protected_resource [auth_cb]: /developers/definitive_guide/authentication_callback