Project Thunder is a modern, identity management service by WSO2. It empowers you to design tailored login, registration, and recovery flows using a flexible identity flow designer.
Thunder secures users, applications, services, and AI agents by managing their identities and offering a complete suite of supporting capabilities.
Designed for extensibility, scalability, and seamless containerized deployment, Thunder integrates naturally with microservices and DevOps environments—serving as the core identity layer for your cloud platform.
- ✅ Standards-Based
- OAuth 2/ OpenID Connect (OIDC): Client Credentials, Authorization Code, Refresh Token
- 🔗 Login Options:
- Basic Authentication (Username and Password)
- Social Logins
- Login with GitHub
- Login with Google
- Login with SMS OTP
- 📝 Registration Options:
- Username and Password Registration
- Social Registration
- Register with GitHub
- Register with Google
- SMS OTP Registration
- 🌐 RESTful APIs:
- App Native Login/ Registration
- User Management
- Application Management
- Identity Provider Management
- Message Notification Sender Management
Follow these steps to download the latest release of WSO2 Thunder and run it locally.
Download thunder_<os>_<arch>-<version>.zip from the latest release for your operating system and architecture.
For example, if you are using a MacOS machine with a Apple Silicon (ARM64) processor, you would download thunder_macos_arm64-<version>.zip.
-
Unzip the downloaded file using the following command:
unzip thunder-<os>_<arch>-<version>.zip
-
Navigate to the unzipped directory:
cd thunder-<os>_<arch>-<version>/
-
Start the product using the following command:
-
If you are using a Linux or macOS machine:
bash start.sh
-
If you are using a Windows machine:
start.bat
-
To quickly get started with WSO2 Thunder, you can use the sample app provided with the product. Follow these steps to download and run the sample app.
Download thunder-sample-app-<version>.zip from the latest release.
unzip thunder-sample-app-<version>.zip
cd thunder-sample-app-<version>/
npm installOpen the runtime.json file in the thunder-sample-app-/dist directory and update the configurations as per your setup. The default configurations should work for most cases, but you can customize the following properties:
applicationID: The ID of the application you want to use for authentication. By default, it is set to550e8400-e29b-41d4-a716-446655440000.flowEndpoint: The endpoint for the flow execution API. By default, it is set tohttps://localhost:8090/flow/execute.
npm startOpen your browser and navigate to https://localhost:3000 to see the sample app in action.
Create a user in the system to tryout the authentication flows. You can use the following cURL command to create a user with the required attributes.
curl -kL -H 'Content-Type: application/json' https://localhost:8090/users \
-d '{
"organizationUnit": "456e8400-e29b-41d4-a716-446655440001",
"type": "superhuman",
"attributes": {
"username": "thor",
"password": "thor@123",
"email": "thor@thunder.sky",
"firstName": "Thor",
"lastName": "Odinson",
"age": 1534,
"abilities": [
"strength",
"speed",
"healing"
],
"address": {
"city": "Asgard",
"zip": "00100"
}
}
}'curl -k -X POST https://localhost:8090/oauth2/token \
-d 'grant_type=client_credentials' \
-u 'client123:secret123'Authorization code flow requires you to setup a gate client to handle the login and error redirection. Add the following configurations to the deployment.yaml file to configure your own gate client.
gate_client:
hostname: "localhost"
port: 9090
scheme: "https"
login_path: "/login"
error_path: "/error"-
Open the following URL in your browser:
https://localhost:8090/oauth2/authorize?response_type=code&client_id=client123&redirect_uri=https://localhost:3000&scope=openid&state=state_1
-
Enter the credentials of the user you created in the first step.
-
After successful authentication, you will be redirected to the redirect URI with the authorization code and state.
https://localhost:3000/?code=<code>&state=state_1
-
Copy the authorization code and exchange it for an access token using the following cURL command:
curl -k -X POST 'https://localhost:8090/oauth2/token' \ -u 'client123:secret123' \ -d 'grant_type=authorization_code' \ -d 'redirect_uri=https://localhost:3000' \ -d 'code=<code>'
- Client ID:
client123 - Client Secret:
secret123
- Client ID:
If the refresh grant is enabled for the application, a refresh token will be issued along with the access token. The refresh token can be used to obtain a new access token without requiring the user to log in again. Use the following cURL command to refresh an access token:
curl -k -X POST 'https://localhost:8090/oauth2/token' \
-u 'client123:secret123' \
-d 'grant_type=refresh_token' \
-d 'refresh_token=<refresh_token>'Open the sample app in your browser and enter the username and password you created in the first step. If the login is successful, you will be redirected to the home page of the sample app with the access token.
-
Create an OAuth application in your Google account following the instructions given in the Google documentation.
- Configure the Authorized origin and Redirect URI as per your application.
- Copy the Client ID and Client Secret.
-
Update the system created Google IDP by invoking the IDP management API with the following cURL command. Make sure to replace
<client_id>,<client_secret>, and<app_callback_url>with the values you copied from your Google OAuth application.curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/identity-providers/550e8400-e29b-41d4-a716-446655440002 \ -d '{ "id": "550e8400-e29b-41d4-a716-446655440001", "name": "Google", "description": "Login with Google", "properties": [ { "name": "client_id", "value": "<client_id>", "is_secret": false }, { "name": "client_secret", "value": "<client_secret>", "is_secret": true }, { "name": "redirect_uri", "value": "<app_callback_url>", "is_secret": false }, { "name": "scopes", "value": "openid,email,profile", "is_secret": false } ] }'
Note: Refer Identity Provider Configuration Guide for more details on configuring identity providers.
-
Update the system default application to use the Google login template by invoking the application management API with the following cURL command.
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_google" }'
Note: Refer Authentication Flow Customization Guide for more details on customizing authentication flows.
-
Open the sample app in your browser and click on the "Continue with Google" button. You will be redirected to the Google login page. Enter your Google credentials and authorize the application.
-
If the login is successful, you will be redirected to the home page of the sample app with the access token.
-
Create an OAuth application in your Github account following the instructions given in the Github documentation.
- Configure home page and callback URLs as per your application.
- Copy the Client ID and Client Secret.
-
Update the system created github IDP by invoking the IDP management API with the following cURL command. Make sure to replace
<client_id>,<client_secret>, and<app_callback_url>with the values you copied from your GitHub OAuth application.curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/identity-providers/550e8400-e29b-41d4-a716-446655440001 \ -d '{ "id": "550e8400-e29b-41d4-a716-446655440001", "name": "Github", "description": "Login with Github", "properties": [ { "name": "client_id", "value": "<client_id>", "is_secret": false }, { "name": "client_secret", "value": "<client_secret>", "is_secret": true }, { "name": "redirect_uri", "value": "<app_callback_url>", "is_secret": false }, { "name": "scopes", "value": "user:email,read:user", "is_secret": false } ], }'
Note: Refer Identity Provider Configuration Guide for more details on configuring identity providers.
-
Update the system default application to use the Github login template by invoking the application management API with the following cURL command.
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_github" }'
Note: Refer Authentication Flow Customization Guide for more details on customizing authentication flows.
-
Open the sample app in your browser and click on the "Continue with GitHub" button. You will be redirected to the GitHub login page. Enter your GitHub credentials and authorize the application.
-
If the login is successful, you will be redirected to the home page of the sample app with the access token.
SMS One-Time Password (OTP) authentication allows users to authenticate using a one-time code sent to their mobile number. Prior to using SMS OTP, you need to configure a message provider to send SMS messages. Follow the steps below to set up SMS OTP authentication.
Configure a message provider to send SMS messages. You can use services like Twilio, Vonage, or a custom service of your choice.
curl -kL -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/notification-senders/message \
-d '{
"name": "Custom SMS Sender",
"description": "Sender for sending SMS messages",
"provider": "custom",
"properties": [
{
"name": "url",
"value": "<custom_sms_provider_url>",
},
{
"name": "http_method",
"value": "POST"
},
{
"name": "content_type",
"value": "JSON"
}
]
}'Note: Refer Message Provider Configuration Guide for more details on configuring message providers.
Update the senderName property in the auth_flow_config_sms flow definition to use your configured message sender.
Update the system application to use the SMS OTP authentication flow template:
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \
--data '{
"id": "550e8400-e29b-41d4-a716-446655440000",
"name": "Test SPA",
"description": "Initial testing App",
"client_id": "client123",
"client_secret": "***",
"callback_url": [
"https://localhost:3000"
],
"supported_grant_types": [
"client_credentials",
"authorization_code"
],
"auth_flow_graph_id": "auth_flow_config_sms"
}'Note: Refer Authentication Flow Customization Guide for more details on customizing authentication flows.
Create a user with a mobileNumber attribute to receive SMS OTP:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/users \
-d '{
"organizationUnit": "456e8400-e29b-41d4-a716-446655440001",
"type": "superhuman",
"attributes": {
"username": "thor",
"password": "thor@123",
"email": "thor@thunder.sky",
"firstName": "Thor",
"lastName": "Odinson",
"age": 1534,
"abilities": [
"strength",
"speed",
"healing"
],
"address": {
"city": "Asgard",
"zip": "00100"
},
"mobileNumber": "+94xxxxxxxxx"
}
}'-
Initiate the authentication flow with your application ID:
curl -kL -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "applicationId": "550e8400-e29b-41d4-a716-446655440000" }'
You'll receive a response with a flow ID and username input request.
-
Provide the username to continue the flow:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "username": "thor" } }'
An OTP will be sent to the user's mobile number.
-
Complete authentication by providing the OTP:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "otp": "696546" } }'
-
If the OTP is valid, you will receive a response with the auth assertion.
Self-registration allows users to create their own accounts. Open the sample app in your browser and click on the "Sign up" button. You will be presented with the registration options based on the configured registration flow for the application.
When you configure an authentication flow for an application, Thunder automatically assigns the equivalent registration flow. For example, if you set auth_flow_graph_id to auth_flow_config_basic, the system will automatically use registration_flow_config_basic for registration.
Note: Refer Registration Flow Customization Guide for more details on configuring registration flows.
This section provides a detailed walkthrough of the authentication flows supported by WSO2 Thunder. You can try out these flows using the sample app provided with the product or by using the cURL commands provided below.
WSO2 Thunder supports app native authentication flows, allowing users to execute login flows via REST APIs. This is particularly useful for mobile and desktop applications that require a native login experience.
Note: Refer Authentication Flow Customization Guide for more details on customizing authentication flows.
-
Create a user in the system if you haven't already. You can use the following cURL command to create a user with the required attributes.
curl -kL -H 'Content-Type: application/json' https://localhost:8090/users \ -d '{ "organizationUnit": "456e8400-e29b-41d4-a716-446655440001", "type": "superhuman", "attributes": { "username": "thor", "password": "thor@123", "email": "thor@thunder.sky", "firstName": "Thor", "lastName": "Odinson", "age": 1534, "abilities": [ "strength", "speed", "healing" ], "address": { "city": "Asgard", "zip": "00100" } } }'
-
Create an application or update the existing system default application to use the basic auth login template. You can use the following cURL command to update the default application.
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000' \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_basic" }'
-
Start login flow for the application with the following cURL command:
curl -kL -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "applicationId": "<application_id>" }'
You'll receive a response similar to the following:
{ "flowId": "db93a19e-c23f-4cfc-a45f-0e0bc157f6d5", "flowStatus": "PROMPT_ONLY", "type": "VIEW", "data": { "inputs": [ { "name": "username", "type": "string", "required": true }, { "name": "password", "type": "string", "required": true } ] } } -
Make the second cURL request to complete the login flow. Make sure to replace
<flow_id>with theflowIdreceived in the previous response. Also, replace theusernameandpasswordwith the credentials of the user you created in the first step.curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "username": "thor", "password": "thor@123" } }'
-
If the login is successful, you will receive a response with the auth assertion.
-
Create an OAuth application in your Google account following the instructions given in the Google documentation.
- Configure the Authorized origin and Redirect URI as per your application.
- Copy the Client ID and Client Secret.
-
Update the system created Google IDP by invoking the IDP management API with the following cURL command. Make sure to replace
<client_id>,<client_secret>, and<app_callback_url>with the values you copied from your Google OAuth application.curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/identity-providers/550e8400-e29b-41d4-a716-446655440002 \ -d '{ "id": "550e8400-e29b-41d4-a716-446655440001", "name": "Google", "description": "Login with Google", "properties": [ { "name": "client_id", "value": "<client_id>", "is_secret": false }, { "name": "client_secret", "value": "<client_secret>", "is_secret": true }, { "name": "redirect_uri", "value": "<app_callback_url>", "is_secret": false }, { "name": "scopes", "value": "openid,email,profile", "is_secret": false } ] }'
Note: Refer Identity Provider Configuration Guide for more details on configuring identity providers.
-
Create an application or update the existing system default application to use the Google login template. You can use the following cURL command to update the default application.
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_google" }'
-
Start login flow for the application with the following cURL command:
curl -kL -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "applicationId": "<application_id>" }'
You'll receive a response similar to the following:
{ "flowId": "80d57e64-8082-4096-bb0e-22b2187f8265", "flowStatus": "INCOMPLETE", "type": "REDIRECTION", "data": { "redirectURL": "<google_auth_redirect_url>", "inputs": [ { "name": "code", "type": "string", "required": true }, { "name": "nonce", "type": "string", "required": false } ], "additionalData": { "idpName": "Google" } } } -
Open the
redirect_urlin your browser. You will be redirected to the Google login page. Enter your Google credentials and authorize the application. -
After successful authentication, you will be redirected to the redirect URI with the authorization code, state and other parameters.
https://localhost:3000/?code=<code>&state=80d57e64-8082-4096-bb0e-22b2187f8265
-
Copy the authorization code and make the second cURL request to complete the login flow. Make sure to replace
<flow_id>with theflowIdreceived in the previous response.curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "code": "<code>" } }'
-
If the login is successful, you will receive a response with the auth assertion.
-
Create an OAuth application in your Github account following the instructions given in the Github documentation.
- Configure home page and callback URLs as per your application.
- Copy the Client ID and Client Secret.
-
Update the system created github IDP by invoking the IDP management API with the following cURL command. Make sure to replace
<client_id>,<client_secret>, and<app_callback_url>with the values you copied from your GitHub OAuth application.curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/identity-providers/550e8400-e29b-41d4-a716-446655440001 \ -d '{ "id": "550e8400-e29b-41d4-a716-446655440001", "name": "Github", "description": "Login with Github", "properties": [ { "name": "client_id", "value": "<client_id>", "is_secret": false }, { "name": "client_secret", "value": "<client_secret>", "is_secret": true }, { "name": "redirect_uri", "value": "<app_callback_url>", "is_secret": false }, { "name": "scopes", "value": "user:email,read:user", "is_secret": false } ] }'
Note: Refer Identity Provider Configuration Guide for more details on configuring identity providers.
-
Create an application or update the existing system default application to use the GitHub login template. You can use the following cURL command to update the default application.
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_github" }'
-
Start login flow for the application with the following cURL command:
curl -kL -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "applicationId": "<application_id>" }'
You'll receive a response similar to the following:
{ "flowId": "80d57e64-8082-4096-bb0e-22b2187f8265", "flowStatus": "INCOMPLETE", "type": "REDIRECTION", "data": { "redirectURL": "<github_auth_redirect_url>", "inputs": [ { "name": "code", "type": "string", "required": true } ], "additionalData": { "idpName": "Github" } } } -
Open the
redirect_urlin your browser. You will be redirected to the GitHub login page. Enter your GitHub credentials and authorize the application. -
After successful authentication, you will be redirected to the redirect URI with the authorization code and state.
https://localhost:3000/?code=<code>&state=80d57e64-8082-4096-bb0e-22b2187f8265
-
Copy the authorization code and make the second cURL request to complete the login flow. Make sure to replace
<flow_id>with theflowIdreceived in the previous response.curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "code": "<code>" } }'
-
If the login is successful, you will receive a response with the auth assertion.
-
Configure a message provider to send SMS messages. You can use services like Twilio, Vonage, or a custom service of your choice.
curl -kL -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/notification-senders/message \ -d '{ "name": "Custom SMS Sender", "description": "Sender for sending SMS messages", "provider": "custom", "properties": [ { "name": "url", "value": "<custom_sms_provider_url>", }, { "name": "http_method", "value": "POST" }, { "name": "content_type", "value": "JSON" } ] }'
Note: Refer Message Provider Configuration Guide for more details on configuring message providers.
-
Update the system application to use the SMS OTP authentication flow:
curl -kL -X PUT -H 'Content-Type: application/json' -H 'Accept: application/json' https://localhost:8090/applications/550e8400-e29b-41d4-a716-446655440000 \ --data '{ "id": "550e8400-e29b-41d4-a716-446655440000", "name": "Test SPA", "description": "Initial testing App", "client_id": "client123", "client_secret": "***", "callback_url": [ "https://localhost:3000" ], "supported_grant_types": [ "client_credentials", "authorization_code" ], "auth_flow_graph_id": "auth_flow_config_sms" }'
-
Create a user with a mobile number attribute to receive SMS OTP:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/users \ -d '{ "organizationUnit": "456e8400-e29b-41d4-a716-446655440001", "type": "superhuman", "attributes": { "username": "thor", "password": "thor@123", "email": "thor@thunder.sky", "firstName": "Thor", "lastName": "Odinson", "mobileNumber": "+94xxxxxxxxx" } }'
-
Start the login flow for the application:
curl -kL -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "applicationId": "<application_id>" }'
You'll receive a response prompting for username input.
-
Provide the username to continue the flow:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "username": "thor" } }'
An OTP will be sent to the user's mobile number.
-
Complete authentication by providing the OTP:
curl -kL -H 'Content-Type: application/json' https://localhost:8090/flow/execute \ -d '{ "flowId": "<flow_id>", "inputs": { "otp": "696546" } }'
-
If the OTP is valid, you will receive a response with the auth assertion.
- Go 1.24+
- Node.js 20+
- Build the product with tests using the following command:
make all- Go 1.24+
- Node.js 20+
- Clone the repository:
git clone https://github.com/asgardeo/thunder
cd thunder- Run the following command to start the product in development mode:
make run- The product will start on
https://localhost:8090.
-
Navigate to the sample app directory:
cd samples/apps/oauth -
Create a file
.envin the pathsamples/apps/oauth/and add below values.VITE_REACT_APP_SERVER_FLOW_ENDPOINT=https://localhost:8090/flow VITE_REACT_APPLICATIONS_ENDPOINT=https://localhost:8090/applications VITE_REACT_APP_AUTH_APP_ID=550e8400-e29b-41d4-a716-446655440000 VITE_REACT_APP_REDIRECT_BASED_LOGIN=false -
Install the dependencies:
npm install
-
Run the sample app using the following command:
npm run dev
-
Open your browser and navigate to
http://localhost:5173to see the sample app in action.
-
Create a Docker container for PostgreSQL with
thunderdbdatabase.docker run -d -p 5432:5432 --name postgres \ -e POSTGRES_USER=asgthunder \ -e POSTGRES_PASSWORD=asgthunder \ -e POSTGRES_DB=thunderdb \ postgres
-
Create the
runtimedbin the same PostgreSQL container.docker exec -it postgres psql -U asgthunder -d thunderdb -c "CREATE DATABASE runtimedb;"
-
Populate the
thunderdbdatabase with the required tables and data.docker exec -i postgres psql -U asgthunder -d thunderdb < backend/dbscripts/thunderdb/postgres.sql
-
Populate the
runtimedbdatabase with the required tables and data.docker exec -i postgres psql -U asgthunder -d thunderdb < backend/dbscripts/runtimedb/postgres.sql
- Open the
backend/cmd/server/repository/conf/deployment.yamlfile. - Update the
databasesection to point to the PostgreSQL database:
database:
identity:
type: "postgres"
hostname: "localhost"
port: 5432
name: "thunderdb"
username: "asgthunder"
password: "asgthunder"
sslmode: "disable"
runtime:
type: "postgres"
hostname: "localhost"
port: 5432
name: "runtimedb"
username: "asgthunder"
password: "asgthunder"
sslmode: "disable"make runThe product will now use the PostgreSQL database for its operations.
Licenses this source under the Apache License, Version 2.0 (LICENSE), You may not use this file except in compliance with the License.
(c) Copyright 2025 WSO2 LLC.
